Skip to main content
Glama

verify_record

Read-only

Free. Use for a supplied signed protocol record or demonstration record, not published JWS issuer-status checks. Verify an AuthiChain signed provenance record with the open reference verifier. Pass id "polygon-anchor-1" for the published demonstration record, or pass your own record and anchor JSON. Returns verified, valid-unanchored, or invalid, plus whether the transaction carries the record hash. It does not inspect a physical product.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPublished record id. Only "polygon-anchor-1" exists.
anchorNoAnchor JSON: { recordHash, chain: "polygon:137", txHash }. Optional.
recordNoA signed AuthiChain provenance record (JSON).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond that: it discloses cost ('Free'), the exact outcome vocabulary (verified, valid-unanchored, invalid, plus whether the transaction carries the record hash), and the explicit negative that it does not inspect a physical product. It stops short of describing error handling or what happens when anchor is omitted, which keeps it from a 5.

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?

Four sentences, front-loaded with the core verb and the exclusion, with no duplicated schema content. The leading one-word fragment 'Free.' is slightly choppy but does convey useful information early.

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?

There is no output schema, but the description enumerates the possible return verdicts, which compensates well. With all three parameters documented at 100% coverage and annotations covering safety, the definition gives an agent everything needed to call it correctly; only edge-case behavior 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%, so each parameter already carries its own description; baseline is 3. The description does add the either/or mode ('Pass id "polygon-anchor-1" ... or pass your own record and anchor JSON'), which clarifies how the three parameters combine, but it adds no format or validation detail beyond the schema.

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 resource — 'Verify an AuthiChain signed provenance record with the open reference verifier' — and explicitly bounds the scope by excluding 'published JWS issuer-status checks' and physical product inspection. An agent can tell this apart from verify/verify_attestation without opening any schema.

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

Usage Guidelines4/5

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

It states when to use it ('a supplied signed protocol record or demonstration record') and when not to ('not published JWS issuer-status checks'), and even explains the demo path via id "polygon-anchor-1" versus supplying your own record plus anchor JSON. The only gap is that it doesn't name the specific sibling tool to use for the excluded JWS issuer-status case.

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.