Skip to main content
Glama

StatuteWire

verify_receipt

Read-only

Checks a StatuteWire receipt JSON (the whole file text or object): hash, canonical form, Ed25519 signature against StatuteWire's published key, and roster totals. Free, not metered. VALID means the file is exactly as StatuteWire signed it; it says nothing about whether the practitioner is clean. A receipt signed with the SAMPLE key is reported as SAMPLE, never as valid. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

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": {
      "receipt": "<receipt>"
    },
    "name": "verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesThe receipt JSON file contents, as a string or an object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that verification is free and unmetered, requires a Bearer sw_live/sw_test key, and returns an error pointing to how_to_get_access when unauthenticated. It also explains that SAMPLE-key signatures are never reported as valid and that VALID does not imply a clean practitioner.

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?

The description is front-loaded with the action and then supplies only high-value caveats: cost, validity semantics, SAMPLE handling, and authentication. Although it is a dense paragraph rather than a list, each sentence carries operational meaning.

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?

For a one-parameter read-only verifier with no output schema, the description covers authentication, cost, key status semantics, and the main valid result. It stops short of describing the full error or invalid-response shape, leaving a modest gap.

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?

There is one parameter and schema description coverage is 100%, so the schema already defines 'receipt' as a string or object; the description only restates that it is the whole file text or object. 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 gives a specific verb-resource pair, 'Checks a StatuteWire receipt JSON,' and enumerates the checks performed: hash, canonical form, Ed25519 signature, and roster totals. That is enough to separate it from retrieval tools like get_receipt, which fetch rather than validate a supplied file.

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?

It implies the tool is for validating a receipt you already have and notes it is free and unmetered, but it does not explicitly say when to use it instead of get_receipt or when not to use it. The caveats about VALID and SAMPLE improve interpretation without providing explicit routing guidance.

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.

Resources