Skip to main content
Glama

StatuteWire

get_receipt

Read-only

Fetches a signed receipt as JSON: either a practitioner receipt by file name (the .json file name from a screening result, for a practitioner on your roster) or a monthly roster receipt (roster_id + period YYYY-MM, built from your latest complete run). Free (rate limited, not metered). A sandbox or non-production receipt is labelled as such or UNSIGNED and proves nothing. Check it with verify_receipt. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

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

Input Schema

NameRequiredDescriptionDefault
fileNoPractitioner receipt file name ending in .json.
periodNoMonth, YYYY-MM.
roster_idNoRoster id (from your account). Use with period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint; the description adds substantial context beyond them: the call is free but rate limited and not metered, sandbox or non-production receipts are labelled UNSIGNED and prove nothing, and the exact auth header forms (Bearer sw_live_… / sw_test_…) with the error path when missing. That is exactly the behavioral detail annotations cannot carry.

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?

Purpose and mode selection are front-loaded in the first sentence, and the trailing sentences cover trust, verification, and auth without filler. The dense semicolon-and-parenthetical packing makes it slightly harder to scan than it needs to be, but no sentence is wasted.

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?

With no output schema, the description still conveys the return is a signed JSON receipt whose signature status is self-labelled (UNSIGNED for sandbox), plus the auth requirement and the verification next step. For a three-optional-parameter read tool that is nearly complete, missing only a hint about how the two modes' responses differ in shape.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by binding parameters to semantics: file must be the .json name taken from a screening result for a practitioner on your roster, and roster_id + period must correspond to your latest complete run. It does not add format detail beyond the schema's YYYY-MM pattern, which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetches a signed receipt as JSON" gives a specific verb and resource, then immediately enumerates the two distinct retrieval modes (practitioner receipt by file name vs. monthly roster receipt via roster_id + period). An agent can distinguish this from verify_receipt and screen_* siblings without opening any schema.

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

Usage Guidelines4/5

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

It states the conditions that select each mode: a practitioner on your roster with a .json name from a screening result, or a roster receipt built from your latest complete run. It also routes the agent onward ("Check it with verify_receipt") and names how_to_get_access as the auth fallback, though it never states an explicit when-not-to-use case.

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