get_sample_receiptA genuine signed receipt from the sample workspace (demo key), for trying verification.
| Name | Required | Description | Default |
|---|---|---|---|
| outcome | No | Pick a sample with this outcome. A BLOCKED receipt was signed without the call reaching the provider. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that the receipt is from a sample workspace with a demo key, providing context beyond annotations. However, no additional behavioral details (e.g., response structure, rate limits) are disclosed. The description does not contradict annotations (annotation_contradiction=false).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one sentence with no wasted words. It conveys the essential purpose and source in a concise manner. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity (one optional parameter, no output schema, clear annotations), the description is fairly complete. It explains what the tool returns and why. A minor improvement would be specifying the return type (e.g., 'receipt object'), but it is not critical for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: the single optional parameter 'outcome' has a description in the schema explaining the enum values. The tool description does not add any extra meaning beyond the schema. Baseline is 3 when schema fully describes parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a genuine signed receipt from the sample workspace for trying verification. This distinguishes it from sibling tools like list_my_receipts (lists user's receipts) and verify_receipt (verifies receipts). The verb 'get' and resource 'sample receipt' are specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions 'for trying verification', which implies a usage scenario, but does not explicitly state when to use this tool over alternatives or when not to use it. No sibling tool comparisons or exclusions are provided. The usage guidance is adequate but minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear distinct jobs: decode, verify, get, list, summarize. The only mildly overlapping pairs are decode_receipt vs explain_attestation_format and verify_receipt vs verify_evidence_pack, but the scopes are well described.
The dominant pattern is verb_noun: decode_receipt, get_public_key, list_my_receipts, verify_receipt. workspace_summary breaks the pattern by being noun-only, but the rest are consistent enough to be predictable.
10 tools is well within the ideal range for a focused attestation and receipt-verification server. Each tool serves a distinct operation from fetching samples and keys to decoding, verifying, listing, and summarizing receipts.
The read/verify workflow is well covered: format explanation, decoding, single-receipt verification, pack verification, sample artifacts, workspace listing, and summary. The main gap is that transparency proofs can be retrieved but there is no corresponding tool for independently verifying a transparency proof.