Assistant tool

erpsav_recovery_playbook

erpsav_recovery_playbook searches ERPSav's playbooks for money a business already lost, such as duplicate payments and card fees. No account is needed.

Updated November 16, 2026

Website
ERPSav · erpsav.com
Class
Read · no account needed
Returns
playbooks[]: slug, title, lead, points[], url

ERPSav's playbook for recovering money a business already lost (no account needed): duplicate payments, vendor credits, lease charges, card fees, warranty claims and more, with the steps.

Where you can call it

Inputs

ArgumentTypeNotes
querystring ≤80The problem, e.g. duplicate invoice.

Example request

POST https://onelifevibe.com/mcp/free

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "erpsav_recovery_playbook",
    "arguments": {
      "query": "<query>"
    }
  }
}

Other ERPSav tools

What it does

erpsav_recovery_playbook searches ERPSav's playbooks for recovering money a business already lost. You give it a short description of the problem, and it returns matching playbooks with the steps. The topics include duplicate payments, vendor credits, lease charges, card fees, warranty claims and more. No account is needed.

Use it when someone wants a concrete recovery path, not a definition. The result is a read-only list: slug, title, lead, points and url. points holds the steps. url takes you to the full playbook on erpsav.com. The tool changes nothing.

When an assistant should call it

When a user asks how to get back money the business overpaid or was charged, call this tool. A query like duplicate invoice, vendor credit or lease charge is enough. It fits questions about invoices, leases, card fees and warranty claims. For terms, use erpsav_define_term. For payment terms, use erpsav_payment_terms.

Call it through an MCP client when you need ERPSav's own recovery steps. If the user asks for account-specific figures or history, this tool cannot supply them: the account connector calls it with no token or identity, and it never returns account data. It is a Read tool, so it is safe to call while you are still gathering context.

Inputs and an example call

The only input is query. It is required, a string of up to 80 characters, and should name the problem, for example duplicate invoice. Keep it short. There is no plan requirement and no sign-in on the free connector.

Call it at https://onelifevibe.com/mcp/free with method tools/call. Set params.name to erpsav_recovery_playbook and params.arguments.query to your problem, for example duplicate invoice. Keep the request id set to 1 in a simple test. The same tool is served at https://onelifevibe.com/mcp, but there it is called with no token or identity, so it never returns account data.

What comes back

On success you get playbooks[], a list. Each entry has slug, title, lead, points[] and url. The slug names the playbook in the result. title and lead give the short label and opening text. points[] holds the steps. url is the playbook page on erpsav.com.

If several playbooks match, show the title and lead and let the user pick. Use points as the outline of the steps, then link to url for the full playbook. The response is playbook content only. It contains no account data.

Errors, limits and safety

query is required and must be 80 characters or fewer. A missing or longer query is not valid input. The free connector is rate-limited, so if you hit the limit, retry later. It needs no sign-in.

The account connector at https://onelifevibe.com/mcp serves the tool too, but with no token or identity, so it never returns account data. No plan is needed. The tool is not destructive and is idempotent: repeating a call does not change anything.

The tool switches itself on when erpsav.com lists it as an anonymous tool. Until then, the connectors do not offer it. If your client does not list erpsav_recovery_playbook, check erpsav.com before you change your integration.

Questions

Do I need an ERPSav account to use erpsav_recovery_playbook?

No. The tool needs no account, and the free connector needs no sign-in. On the account connector it is called with no token or identity, so it never returns account data.

What should I put in the query for erpsav_recovery_playbook?

Put the problem in up to 80 characters, for example duplicate invoice. The query is required, and a short problem name is enough to search the playbooks.

Why is erpsav_recovery_playbook missing from the connector?

It switches itself on when erpsav.com lists it as an anonymous tool. Until then, the connectors do not offer it. Check erpsav.com if your client does not list the tool.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.