InvoiceParser Pro

Preview: Mark invoices as distinct

preview_dismiss_duplicate_group

Read-onlyIdempotent

Prepare marking the selected invoices as distinct rather than duplicates. Requires confirmation; invoices are retained. 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_dismiss_duplicate_group"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ('invoices are retained', 'does not apply the change'). It adds real value beyond the annotations by disclosing a five-minute token expiry and that the preview is exact, though it says nothing about what happens if the token lapses or what the preview payload contains.

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?

Three short sentences, front-loaded with the effect, then the confirmation requirement, then the return contract. No filler and nothing repeated from the annotations.

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?

Covers the return contract reasonably (preview plus token) despite having no output schema, but for a single opaque nested object at 0% schema coverage it leaves the agent guessing about input grouping rules and token-consumption behavior. Adequate rather than complete.

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%, so the description carries the burden and mostly does not: 'the selected invoices' never explains that a minimum of two and at most fifty UUIDs are required, nor that the invoices must belong to the same duplicate group for the preview to be meaningful. Those constraints live only as minItems/maxItems in the schema, with no semantic framing.

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?

Uses a specific verb-plus-resource ('prepare marking the selected invoices as distinct rather than duplicates') and immediately frames the operation as a preview that does not apply the change, which cleanly separates it from the sibling dismiss_duplicate_group. An agent can tell which of the two to call first without opening the schema.

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?

States the prerequisite flow implicitly and correctly: 'requires confirmation' and 'it does not apply the change' tell the agent this is the confirmation-token step. It does not explicitly name dismiss_duplicate_group (or list_duplicate_groups) as the follow-up/feeder, so the alternative stays inferred rather than stated.

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?