Skip to main content
Glama

Impact receipts

impact_receipts
Read-onlyIdempotent

Logged changes for one website (notes, releases from the deploy hook, Stripe price changes, Google click drops), newest first, the newest of them with a receipt (a long list leaves the oldest without one): revenue per currency, signups and visitors over the same number of days before vs after, the top mover, and a confidence label. status is waiting (under a day old), collecting (the after window is still open) or ready. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
daysNochanges logged in the last N days, 1-366; default 90
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

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's added value here is real: it discloses newest-first ordering, the fact that only the newest changes carry receipts so old entries return partial data, and the three status states with their meanings (waiting <1 day, collecting, ready). The one gap is that 'confidence label' is never explained — what the labels are or how to interpret a low-confidence receipt.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single long run-on sentence with nested parentheses, which makes it dense to parse despite being front-loaded with the resource description. Every clause carries information, but the receipt contents list and the status list would be far more scannable as separate sentences or a short list.

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, return values need not be explained, yet the description still characterizes ordering, partial-receipt behavior, status lifecycle, and receipt contents — enough to call the tool correctly. The remaining shortfall is the unexplained confidence label and no guidance on what to do when status is collecting rather than ready.

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 coverage is 100%, so the schema already documents both parameters including the 1-366 range and default 90. The description adds oblique meaning by revealing that the same N days also sizes the before-vs-after comparison windows used for signups and visitors, which the schema alone does not state; however this is embedded in prose rather than tied explicitly to the days parameter.

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 names the resource precisely (logged changes plus a computed impact receipt) and enumerates the change types it covers — notes, deploy-hook releases, Stripe price changes, Google click drops — plus what the receipt contains. An agent can tell this is a per-website change/receipt feed rather than a generic analytics dump. It stops short of naming which sibling to use instead (e.g. revenue_moves or insights), so it is clear but not sibling-differentiated.

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?

Usage is implied rather than stated: the parenthetical 'a long list leaves the oldest without one' hints that narrowing the days window is how you get a receipt for older changes, and the status vocabulary tells the agent what state to expect. There is no explicit when-to-use/when-not or pointer to a sibling for pulling raw analytics instead.

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