Skip to main content
Glama

Verify result

verify_result
Read-onlyIdempotent

Recompute a disclosure draft audit hash, notary payload, structural invariants, and framework-pack currency. Pass the prior result 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 compile_disclosure 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 compile_disclosure result, as a JSON string, unchanged."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value by disclosing exactly what is recomputed and checked, which tells the agent this is a validation pass rather than a mutation.

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 verification scope and followed by the one calling instruction. Nothing is redundant or padded.

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?

An output schema exists, so return values need no explanation, and the single-parameter surface is simple. The description covers what is verified and how to supply input; only explicit sequencing with compile_disclosure is left implicit.

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% and the single parameter is fully documented as the unchanged compile_disclosure result. The description reinforces "prior result" and "unchanged," a useful but marginal addition over the schema, so baseline 3 applies.

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 (recompute/verify) and enumerates the concrete artifacts checked: audit hash, notary payload, structural invariants, framework-pack currency. This clearly separates it from compile_disclosure, though it never names that sibling 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?

"Pass the prior result as JSON" implies this runs after compile_disclosure, giving implied sequencing. There is no explicit when-to-use/when-not statement and no named alternative, so guidance is inferred rather than 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.