Invoices to Spreadsheets

Check invoices

check_invoices

Read-only

Use this when the user wants invoices verified without making a file: whether net plus VAT equals the total, whether line items add up, which fields are missing, and which invoices look like duplicates. Returns the findings and totals per currency. Nothing is stored.

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": {
      "invoices": "<invoices>"
    },
    "name": "check_invoices"
  }
}

Input Schema

Name	Required	Description	Default
`invoices`	Yes	Every invoice, one entry each, with values exactly as printed on the document. Use null for anything not printed or not legible; never estimate.

Output Schema

Name	Required	Description	Default
`checks`	Yes
`totals`	Yes
`check_count`	Yes
`invoice_count`	Yes
`line_item_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false; the description reinforces this with 'Nothing is stored', which is the key behavioral reassurance for a validation tool. It also previews the response shape ('findings and totals per currency'), adding value beyond the annotations, though it says nothing about how duplicate detection works or how partial/illegible data affects the result.

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?

Two tight sentences: the trigger and the differentiating condition come first, the checks second, and the outcome/no-storage note last. No filler or restatement of the title.

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?

With full schema coverage, an output schema, and complete annotations, the description supplies the remaining pieces: when to use it, what the checks are, that nothing persists, and what comes back. An agent can select and invoke it correctly without further information.

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?

Schema coverage is 100%, so the structure of the invoices array and its fields is fully documented. The description still adds meaning by telling the agent which field relationships are actually validated (net + VAT = total, line items summing), which is not evident from the schema alone.

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?

States a specific verb (verify) and resource (invoices), then enumerates the exact checks performed: net plus VAT versus total, line-item sums, missing fields, and likely duplicates. The phrase 'without making a file' immediately separates it from the spreadsheet-creation sibling.

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?

Gives an explicit trigger ('when the user wants invoices verified') and an explicit exclusion ('without making a file'), which routes the agent away from create_invoice_spreadsheet. It does not name that sibling directly, so the contrast must be inferred from the condition rather than stated outright.

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

All Invoices to Spreadsheets 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?