InvoiceParser Pro

Preview: Clear exchange-rate annotation

preview_clear_invoice_settlement

Read-onlyIdempotent

Prepare removing an invoice's operational exchange-rate annotation, retaining its original amounts. Requires financial permission and 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_settlement"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that financial permission is required, that confirmation is needed, and that the tool returns an exact preview and a five-minute confirmation token. It also explicitly states that the change is not applied, which is important behavioral context for a read-only preview.

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 description is three tightly written sentences. The core action is front-loaded, followed by prerequisites and return/behavior details with no wasted wording.

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

Completeness4/5

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

For a one-parameter preview tool with no output schema, the description covers the essential workflow, permissions, confirmation token, and non-mutating behavior. The main gap is that it does not add parameter-specific detail despite the schema's lack of parameter descriptions.

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?

The schema has only one parameter and 0% description coverage, so the description must compensate. It refers to 'an invoice's' annotation but does not explain the invoice_id parameter, its UUID format, or what it identifies beyond the obvious invoice context.

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

Purpose4/5

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

The description states a specific action and resource: preparing removal of an invoice's operational exchange-rate annotation while retaining original amounts. It also makes clear that this is a preview and does not apply the change, which helps distinguish it from the actual clear operation. It does not explicitly contrast with preview_set_invoice_settlement, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

The text implies this is the preview step before applying a removal, and it notes permission and confirmation requirements. The returned five-minute confirmation token reinforces the workflow context. However, it does not explicitly name the non-preview alternative or state when not to use this 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?