Skip to main content
Glama

Get a signed receipt

get_receipt
Read-onlyIdempotent

Supporting detail. Show it only after the decision card, collapsed or as a compact table below it, never before. Returns a signed NEXUS NOR v0.3 receipt for one of your own earlier checks. Receipts hold hashes and outcomes only, never what was shared.

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_id": "<receipt_id>"
    },
    "name": "get_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: receipts contain only hashes and outcomes and never the shared content, and only receipts from the caller's own earlier checks are retrievable. That is real disclosure beyond the structured fields, though nothing is said about failure modes for unknown or foreign receipt IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, but the ordering is backwards: the first two are layout instructions for the calling UI rather than tool semantics, and the sentence that actually says what the tool does arrives third. The content is not bloated, but it is not front-loaded.

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 single-parameter read with no output schema, the definition covers what is returned at a meaningful level (signed receipt, hashes and outcomes only, no shared content) and the ownership constraint. The remaining gap — what happens when the receipt_id is unknown or belongs to another caller — is minor.

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 required parameter with 0% schema description coverage — only a UUID regex pattern is supplied. The description only indirectly characterizes receipt_id as identifying one of your own earlier checks; it adds no format, source, or error semantics 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 third sentence states a specific verb and resource: returns a signed NEXUS NOR v0.3 receipt for one of the caller's earlier checks. That is clear enough to distinguish it from siblings like agency_check or describe_ruleset, but the actual purpose is buried behind two sentences of UI presentation instructions, so the tool's identity is not front-loaded.

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?

'For one of your own earlier checks' implies a prerequisite (a prior check must exist) and a scope limit (own receipts only), which is useful. However, 'show it only after the decision card' is output-rendering guidance, not when-to-call guidance, and no alternative tool or exclusion condition is named.

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.