Skip to main content
Glama

receipts_me

Read-only

Receipts for your key: whether THIS key is opted in to a receipt with each paid graph answer, and how its owner turns them on. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
callerNo
agent_idNo
receipt_offerNo
what_a_receipt_isNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / title
      Removed value: -"receipts_meArguments"
    • removedOutput schema / description
      Removed value: -"receipts_me — the calling key's receipt setting and the price (GET /api/v1/receipts/me)."
    • removedOutput schema / properties / agent_id / default
      Removed value: -null
    • removedOutput schema / properties / agent_id / title
      Removed value: -"Agent Id"
    • removedOutput schema / properties / caller / default
      Removed value: -null
    • removedOutput schema / properties / caller / title
      Removed value: -"Caller"
    • removedOutput schema / properties / receipt_offer / default
      Removed value: -null
    • removedOutput schema / properties / receipt_offer / title
      Removed value: -"Receipt Offer"
    • removedOutput schema / properties / what_a_receipt_is / default
      Removed value: -null
    • removedOutput schema / properties / what_a_receipt_is / title
      Removed value: -"What A Receipt Is"
    • removedOutput schema / title
      Removed value: -"ReceiptsMeOut"
  2. Added

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 openWorldHint=false, so safety is covered. The description adds useful context by stating the tool is 'Free' and that it reports on 'THIS key' and its owner, going beyond what the annotations provide.

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?

The description is a single, front-loaded sentence that conveys the core purpose, scope, and cost without any wasted words.

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 an output schema present and no input parameters, the description supplies enough context for an agent to understand what the tool returns and when it is useful. Minor gaps remain around whether 'how its owner turns them on' is returned as instructions or just described.

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 has zero parameters, so the baseline is 4. The empty schema fully covers inputs, and no parameter semantics are needed beyond what is already structured.

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 clearly states that the tool returns receipt opt-in status for the caller's key and explains how the owner can enable receipts. It is specific about the resource (receipts) and scope (THIS key), though it does not explicitly name sibling tools or use a strong verb like 'check' or 'get'.

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?

The description implies usage for checking whether the current key is opted into receipts and finding out how to enable them. However, it does not explicitly say when to use this tool versus alternatives like contribute_receipts or transparency_latest, nor does it provide when-not-to-use guidance.

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