Skip to main content
Glama

Stream Presence — Receipt Verifier

Get a receipt

get_receipt
Read-onlyIdempotent

Fetch one receipt from the public log by id: the log entry (sequence, entry hash) and the receipt object, plus its W3C Verifiable Credential sidecar when one was issued.

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_idYesReceipt id, rcpt_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, closed-world), so the description's added value is the return shape: the log entry fields and the conditional W3C Verifiable Credential sidecar. That conditional return detail is genuinely useful context beyond the annotations, though error/not-found behavior is not covered.

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?

One sentence, front-loaded with the action and scope, then the payload contents. No filler, no restatement of the title, and the conditional sidecar clause is appended where it belongs.

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 tool with no output schema, the description supplies the missing return-value picture (log entry plus receipt plus optional credential), which is the main gap it needed to close. Only the failure mode for an unknown id is left unstated.

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% with a single documented parameter including its rcpt_ prefix, so the schema carries the parameter burden. The description restates "by id" without adding format, validation, or resolution semantics beyond what the schema already says.

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?

Specific verb and resource: "Fetch one receipt from the public log by id", and it enumerates what comes back (log entry with sequence and entry hash, receipt object, optional VC sidecar). It does not name a sibling or state how it differs from verify_receipt, so sibling differentiation is left implicit.

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?

"Fetch one receipt ... by id" implies the single-item lookup case and the qualifier "from the public log" hints at scope, but there is no explicit when-to-use versus when-to-verify guidance and no mention of what happens when the id is unknown. Usage is inferable 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.

Resources