Skip to main content
Glama

Tally by Outpost

Sale receipt

get_receipt
Read-onlyIdempotent

One payment's receipt: the evidence chain that ties it to a visit (first visit, visits before paying, the credited visit, the handle that matched and where), every provider id, and the payment it follows from.

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": {
      "payment_id": "<payment_id>"
    },
    "name": "get_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoThe site's id. Optional: the API key's site is the one read.
payment_idYesThe payment's id, from list_sales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to spend its words on what the response actually contains: the attribution chain (first visit, pre-payment visits, credited visit, matched handle and where), all provider ids, and the originating payment. That is real context beyond the structured fields, with no contradiction.

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?

A single sentence with zero filler, scoping first and detail second. The parenthetical enumeration of evidence-chain items is dense but every element is informative, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey return content, and it does: the specific evidence chain components, provider ids, and the predecessor payment. Combined with full parameter coverage and annotations carrying the safety profile, an agent has enough to call this correctly.

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 description coverage is 100%, including the site default-to-API-key behavior and the payment_id provenance, so the schema carries the parameter burden. The description reinforces 'one payment' but adds no format or filtering semantics beyond what is already documented.

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?

Front-loads a specific scope ('One payment's receipt') and then enumerates the substantive content: attribution evidence chain, provider ids, and the preceding payment. An agent can distinguish this single-payment detail fetch from the list_sales enumeration without opening the schema, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, and no alternatives are named. The only routing hint lives in the schema ('from list_sales'), not in the description text itself.

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