Skip to main content
Glama

verify_batch

Check up to 50 numerical claims in one call by supplying each claim's calculation type, claimed result, inputs, and optional tolerance for deterministic re-calculation.

Instructions

Check up to 50 numerical claims in one call. Each item has calculation_type, claimed_result, inputs and optional tolerance.

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": {
      "requests": "<requests>"
    },
    "name": "verify_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the 50-item ceiling and the per-item shape, which are real constraints. It says nothing about read-only vs. mutating behavior, per-item error handling, partial failure semantics, or whether results are signed (relevant given the verify_and_sign sibling).

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 short sentences, front-loaded with the batch cap and immediately followed by the per-item contract. No filler and nothing that could be cut without losing information.

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?

With an output schema present, return values need no explanation, and the description covers capacity and per-item fields for a one-parameter batch tool. The remaining gap is item-level meaning (valid calculation_type values, tolerance units, behavior on a failing item), which matters because the schema defines none of it.

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 0% and items are declared only as generic objects with additionalProperties, so the description is the sole source of item field names: calculation_type, claimed_result, inputs, and optional tolerance. That compensates substantially for an opaque schema, but it does not define allowed calculation_type values or tolerance semantics, so it is not complete.

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 ('Check') and resource ('numerical claims') plus the batch scope ('up to 50 ... in one call'), which separates it from the single-claim sibling verify_calculation by implication. It never names the sibling explicitly, so the differentiation is inferred from 'batch' rather than stated.

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 phrase 'in one call' plus the 50-item cap implies this is the batched alternative to repeated single verifications, which is useful routing context. There is no explicit when-not guidance, no mention of verify_calculation or verify_and_sign as alternatives, and no stated prerequisites.

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