Skip to main content
Glama

verify_calculation

Independently recalculates a claimed numerical result from supplied inputs and returns passed or failed with the correct value, so agents can catch arithmetic errors before acting.

Instructions

Check a claimed numerical result. Request fields: calculation_type, claimed_result, inputs, optional tolerance. Returns passed/failed and independently calculated result. Claim-vs-source categories (quote_in_text, number_in_text, date_in_text) take source_text you supply plus claim_text (or claimed_result for numbers); they prove only that the supplied text contains the claim, not that it is true.

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": {
      "request": "<request>"
    },
    "name": "verify_calculation"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a valuable behavioral limit — that claim-vs-source categories prove only that the text contains the claim, not that it is true — but omits what values calculation_type accepts, whether the operation has any side effects, and how tolerance is interpreted.

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

Conciseness3/5

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

The purpose is front-loaded in one short sentence and the field list follows logically. However, the return-value sentence repeats what the output schema already declares, and the category clause is compressed into a dense run-on that is harder to parse than it needs to be.

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?

An output schema exists, so the return values need not be explained, and the description does cover the request fields and the category caveat. For a verification tool with a fully undocumented open schema, it still leaves gaps around supported calculation types and tolerance defaults that an agent needs before calling.

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

Parameters3/5

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

Schema coverage is 0% and the schema is an open object, so the description is the only source of field information; it names calculation_type, claimed_result, inputs, tolerance, source_text and claim_text, and marks tolerance as optional. It does not explain the accepted calculation_type values or the expected shape of inputs, leaving the two most consequential fields under-specified.

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?

States a specific verb and resource: 'Check a claimed numerical result,' which tells an agent exactly what the tool produces. It is implicitly distinguished from verification siblings (signing, batch, receipts) by being about numerical claims, but never names those alternatives explicitly.

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

Usage Guidelines3/5

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

The description gives real usage context by enumerating the request fields and explaining that claim-vs-source categories take source_text plus claim_text. It stops short of saying when to choose this over verify_batch or verify_and_sign, and gives no exclusions or prerequisites.

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