Skip to main content
Glama

Verify result

verify_result
Read-onlyIdempotent

Recompute a takeoff audit hash, notary payload, pack currency, and QT9 unit-resolved conservation. Pass the prior result object as JSON.

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": {
      "result_json": "<result_json>"
    },
    "name": "verify_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
result_jsonYesThe full calculate_takeoff result, as a JSON string, unchanged.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / result_json / description
      Added value: +"The full calculate_takeoff result, as a JSON string, unchanged."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the tool recomputes multiple checks and expects the prior result unchanged, but it does not say what happens on mismatch or how verification is reported.

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?

The description is short and front-loaded, with the operation first and the input instruction second. The first sentence is dense with domain jargon, but no sentence is wasted.

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 covering results, annotations covering safety, and a fully described single input, the description provides enough to invoke the tool. The main remaining gap is the lack of explicit usage guidance about when verification should be run.

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 100% for the single result_json parameter, and the schema already specifies it must be the full calculate_takeoff result as an unchanged JSON string. The description's "Pass the prior result object as JSON" is consistent but adds little beyond the schema.

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?

The description uses the specific verb "Recompute" and names four checks (audit hash, notary payload, pack currency, QT9 conservation), making the verification purpose clear. It does not explicitly distinguish this from calculate_takeoff or explain the domain jargon, so it falls short of a 5.

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?

"Pass the prior result object as JSON" implies this is a follow-up verification step after a prior calculation, but the description gives no explicit when-to-use or when-not-to-use guidance relative to calculate_takeoff. The intended usage is inferable but not stated.

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.