Skip to main content
Glama

get_receipt_key

Read-only

Read the site receipt verification key. Pin a trusted copy independently.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
issuerYes
key_idYes
algorithmYes
public_keyYes
canonicalizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 notably idempotentHint=false; the description complements this by telling the agent to pin a trusted copy independently, which signals that the returned key should be captured and held rather than re-fetched and blindly re-trusted. This is meaningful trust-on-first-use context that the annotations alone would not convey. It does not mention key rotation or rate limits explicitly, keeping it short of 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.

Conciseness5/5

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

Two sentences, both front-loaded and load-bearing: the first names the action and resource, the second states the operational caution. No filler or restatement of the tool name.

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 zero-parameter read with an output schema (so return values need not be explained) and full annotation coverage, the description supplies what an agent needs: purpose plus the pinning instruction. A brief note on whether the key rotates or on trust implications would push it to complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is missing because no parameters exist.

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 and resource: 'Read the site receipt verification key.' That is unambiguous and clearly distinct from the catalog/topic siblings, none of which deal with verification keys. It stops short of any explicit contrast with other tools, but the resource itself is unique enough that an agent can select it confidently.

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?

'Pin a trusted copy independently' implies the usage context — obtain the key once and store it out-of-band rather than trusting each response — but never states when to call this versus other retrieval paths, nor any preconditions. The guidance is inferable rather than explicit.

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