Skip to main content
Glama

Receipts Index: free sample row

receipts_sample
Read-only

Calls GET /v1/sample on the Receipts API. Free. Returns one real record row labeled as a sample, with its row id and the row as fields and as CSV. It takes no parameters and is not a purchase.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real context on top: it discloses the underlying HTTP endpoint, that the call costs nothing, that no parameters are accepted, and that the returned row is deliberately labeled as a sample. Auth requirements and rate limits are not mentioned, which keeps 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.

Conciseness4/5

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

Four short sentences, front-loaded with the endpoint and cost, then the return shape, then the parameter/purchase disclaimer. Every sentence carries distinct information; the telegraphic style ('Free.') is efficient rather than sloppy.

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 must describe return values and does: a single sample row with its row id, exposed both as fields and as CSV. For a zero-parameter read-only tool this is nearly complete, with only authentication or call-limit details absent.

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 the baseline is 4. The description explicitly confirms 'It takes no parameters,' matching the empty schema and removing any doubt about hidden required inputs.

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?

States a specific verb and resource ('Calls GET /v1/sample on the Receipts API') and describes exactly what comes back: one real record row labeled as a sample, with row id, fields, and CSV. It also signals its role as the free/non-purchase variant, which implicitly separates it from the paid siblings, though it never names them.

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 'Free' and 'is not a purchase' phrasing implies this is the preview/trial entry point before the paid tools, but that inference is left to the agent. There is no explicit 'use this when…' statement or named alternative such as receipts_index or receipts_pricing.

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.