InvoiceParser Pro

Preview: Clear invoice posting account

preview_clear_invoice_posting_account

Read-onlyIdempotent

Prepare clearing explicit invoice account coding; client/workspace fallbacks remain. Existing export holds are enforced. Requires confirmation. This returns an exact preview and a five-minute confirmation token; it does not apply the change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: a five-minute confirmation token with a stated TTL, an exact preview return, an explicit statement that nothing is applied, and that existing export holds are enforced. "Client/workspace fallbacks remain" is opaque, but the token lifetime and no-op guarantee are exactly the context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and ending with the critical no-apply/token caveat; no filler. Density is offset by cryptic phrasing like "explicit invoice account coding" and "fallbacks remain," which cost clarity without saving words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so the description must carry return semantics; it says "exact preview" plus a token but not what the preview contains or which tool redeems the token. For a confirmation-gated preview in a family of ~40 preview_* siblings, that leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single invoice_id (uuid) parameter, and the description never mentions the input at all — not even that it takes an invoice. With low coverage the description is expected to compensate, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is present but garbled: "Prepare clearing explicit invoice account coding" is jargon that never plainly says it previews clearing an invoice's posting account. The final sentence ("returns an exact preview ... does not apply the change") rescues the intent, but the tool is not explicitly distinguished from sibling clear_invoice_posting_account or preview_set_invoice_posting_account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Requires confirmation" implies a preview-then-confirm flow but never names the tool that consumes the token or when an agent should skip the preview and call clear_invoice_posting_account directly. No exclusions or alternative routing are given despite a dense sibling set of near-identical preview_* tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InvoiceParser Pro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?