InvoiceParser Pro

Select an invoice posting account

set_invoice_posting_account

DestructiveIdempotent

Apply only the exact change returned by preview_set_invoice_posting_account, after the user confirms that preview. Accepts its confirmation_token only; changed or expired records require a new preview. Prepare choosing an active account from this workspace's cached chart. Supplier and account names come from saved records. Reuses review coding: manual vendor rules stay unchanged; otherwise its learned vendor rule/counter is updated. No provider refresh, bill push or payment. Requires confirmation.

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": "set_invoice_posting_account"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important side effects: manual vendor rules stay unchanged, otherwise the learned vendor rule/counter is updated. It also clarifies what does not happen (no provider refresh, bill push, or payment), which is valuable for a destructive mutation.

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

Conciseness5/5

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

The definition is dense but front-loaded: it starts with the core apply-after-preview rule, then adds constraints and side effects. Every sentence carries operational information, with no filler.

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

Completeness5/5

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

For a destructive, idempotent mutation with no output schema, the description covers prerequisites (confirmed preview), token validity, source of account data, rule-update behavior, and explicit non-actions. Nothing essential for correct invocation is missing.

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

Parameters4/5

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

The schema already describes the confirmation_token, but the description adds lifecycle semantics: it accepts only that token, and changed or expired records require a fresh preview. This adds useful meaning beyond the schema, though the token format itself is left to the schema.

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

Purpose5/5

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

The description states a specific action: apply the exact change returned by preview_set_invoice_posting_account after user confirmation. It clearly distinguishes this tool from its preview sibling and from clear_invoice_posting_account by framing it as the confirmation/apply step.

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

Usage Guidelines5/5

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

It explicitly says to apply only the exact change from the preview after the user confirms it, and that changed or expired records require a new preview. This gives clear when-to-use and when-not-to-use guidance tied directly to the sibling preview tool.

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?