Skip to main content
Glama

Agent Verifier — Independent Number Verification

Verify numbers in a finished table or breakdown

verify_numbers

Verify that the numbers in a finished table add up — before you deliver it. Use this when you have produced or received a table, spreadsheet, CSV/TSV or markdown table, a cost breakdown, invoice, quotation or budget, and need an independent check that row totals, column totals and subtotals are arithmetically consistent, or that a list of line items sums to a stated total. Returns every mismatched cell with the recomputed value and the difference, plus a publicly checkable verification receipt (verification ID, UTC time, SHA-256 content hash, and a public verification URL that anyone can use to confirm the check happened). Checks arithmetic consistency only; does not verify source data. Accepts common international formats: accounting negatives in parentheses, currency symbols, semicolon-delimited tables with decimal commas, and percent values. Tables may include formulas: supported formulas are evaluated for the arithmetic check, and every formula is audited for pattern deviations, hardcoded values among formulas and broken references, returned as advisory findings. Every result states its coverage — how many checks ran, the tolerance applied (0.005), and which numeric columns or formulas could not be checked — so a MATCH certifies only the totals that were located and recomputed. It audits finished numbers; it does not build new calculations for you.

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": {
      "content": "<content>"
    },
    "name": "verify_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe finished table (markdown, CSV or TSV) or the "name: value" breakdown text to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the return payload (every mismatched cell with recomputed value and difference), the verification receipt contents (ID, UTC time, SHA-256 hash, public URL), the tolerance (0.005), and the coverage statement that qualifies a MATCH result. It also flags a secondary behavior an agent would not otherwise expect — formula evaluation plus advisory audit findings for hardcoded values and broken references — and openly limits the guarantee to totals that were located.

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?

It is front-loaded correctly — purpose, trigger, return value, then limits and format support — and every paragraph carries real information. It is, however, dense to the point of being two very long sentences, and the closing 'It audits finished numbers; it does not build new calculations for you' restates the earlier 'Checks arithmetic consistency only', so a small amount of material does not earn its place.

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?

There is no output schema and no annotations, so the description must define both behavior and returns; it does, including receipt fields, mismatch reporting, tolerance and coverage semantics. For a one-parameter audit tool it leaves an agent with nothing material unresolved about how to call it or how to read a MATCH versus a mismatch.

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

Parameters5/5

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

Schema coverage is 100% for the single `content` parameter, so the baseline is 3; the description exceeds it by spelling out the accepted syntactic space: accounting negatives in parentheses, currency symbols, semicolon-delimited tables with decimal commas, percent values, and 'name: value' breakdown text. An agent knows what forms of input will parse and what will not, which the schema's one-line description does not convey.

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 names a specific verb and object — verify that numbers in a finished table add up — and enumerates the exact check performed (row totals, column totals, subtotals, line items vs stated total). It also draws a hard boundary against the adjacent capability ('It audits finished numbers; it does not build new calculations for you'), so an agent can tell what class of tool this is 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 Guidelines5/5

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

Usage is stated explicitly with trigger conditions: 'before you deliver it', whenever you have produced or received a table, CSV/TSV, cost breakdown, invoice, quotation or budget. Exclusions are equally explicit — arithmetic consistency only, source data is not verified, no new calculations are built. That is when-to-use, when-not-to-use and boundary-setting in one place.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources