Skip to main content
Glama

Buy a full report from the agent's wallet

buy_report

For a projection that buy_projection paid for, once check_projection shows it done: returns the payment link for its full report, $10, paid from the agent's MPP wallet with a Stripe Shared Payment Token. The full report is a PDF with each candidate's standing in each topic group of campaign activities, each campaign's frame, a win strategy for each candidate, the 51% line, and the sources. The paid answer starts the report; check_projection then gives its state and, once it is done, the link to its PDF. A report that fails refunds its payment. Needs no sign-in.

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": {
      "run_id": "<run_id>"
    },
    "name": "buy_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id of the projection that buy_projection paid for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the $10 price, the payment rail (MPP wallet / Stripe Shared Payment Token), the refund-on-failure behavior, the no-sign-in requirement, and the post-call state loop via check_projection. The main undisclosed risk is repeat invocation — idempotentHint=false implies a second call could incur a second $10 charge, and the description never warns about that.

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?

Front-loads the precondition and the payment facts, which is good, but the middle section restates the same flow twice — 'returns the payment link for its full report' and later 'check_projection then gives its state and, once it is done, the link to its PDF' cover the same ground. The report-contents sentence is a long undifferentiated list that could be tightened.

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?

For a one-parameter purchase tool with no output schema, the description covers price, payment mechanism, refund policy, auth requirements, report contents, and the follow-up state check. An agent has what it needs to decide to call it and what to expect afterwards; only the duplicate-charge question for a non-idempotent purchase is left open.

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% and the single run_id parameter is already documented in the schema as 'the run_id of the projection that buy_projection paid for'. The description's precondition language reinforces that constraint but adds no format, sourcing, or example detail beyond the schema.

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 concrete outcome: returns the payment link for the full report, $10, charged from the agent's MPP wallet via a Stripe Shared Payment Token, and enumerates the report's contents (per-candidate standing, frames, win strategy, 51% line, sources). It is clearly distinct from buy_projection (which pays for the projection) and check_projection (which reports state). The verb is slightly muddled — the name says 'buy_report' but the sentence leads with 'returns the payment link' — leaving mild ambiguity about whether the tool performs the charge or only surfaces the URL.

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?

Gives an explicit prerequisite chain: only for a projection that buy_projection paid for, and only once check_projection shows it done, naming both sibling tools. It does not state a when-not case or what to do if the precondition is unmet, but the sequencing guidance is clear enough to act on.

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