Skip to main content
Glama

check_signed_receipt

Verify AgentVerify receipt integrity by checking for an intact signature from the local issuer.

Instructions

Check whether an AgentVerify receipt has an intact signature from this local issuer.

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": "check_signed_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the important behavioral scope that verification is limited to signature integrity against the local issuer, not a broader trust evaluation. It says nothing about permissions, failure modes, or whether partial/expired receipts are rejected, so gaps remain for a security-sensitive check.

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?

A single front-loaded sentence with no redundant wording; the scope qualifier is placed where it is read first. Its brevity is not padded, though it leaves little structural room for the usage and parameter guidance the tool needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 semantics need not be described, and the core intent is unambiguous. However, for a tool taking an untyped nested receipt with no annotations and no schema descriptions, the definition leaves an agent without enough to know what constitutes a valid input or when this tool applies versus its verify siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'receipt' parameter is an open nested object with additionalProperties: true and 0% schema description coverage, yet the description never indicates what the receipt must contain or which fields are inspected. With the schema doing nothing to explain the payload, the description should compensate and does not.

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 gives a specific verb ('Check whether') and a specific resource ('an AgentVerify receipt ... signature'), plus the scope qualifier 'from this local issuer', which tells the agent this validates signature integrity rather than performing a full trust-chain or calculation verification. It never names a sibling such as verify_batch or verify_calculation to draw the boundary explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this tool over verify_and_sign, verify_batch, or verify_calculation, and no prerequisites or preconditions are given. The 'single receipt / local issuer' framing implies a narrow use case, but the agent must infer that on its own.

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