Skip to main content
Glama

buy_full_teardown

Quote and buy the $9 full teardown for a roast. Step 1: call with just the roast_id — you get the quote and nothing is charged, no checkout session is created. Step 2: only after the user has said yes, call again with confirmPaymentSpend: true to create the Stripe checkout session and get the URL for them to pay at. PageRoast has no accounts and stores no card, so the payment happens on Stripe's own page.

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": {
      "roast_id": "<roast_id>"
    },
    "name": "buy_full_teardown"
  }
}

Input Schema

NameRequiredDescriptionDefault
roast_idYesThe roast_id returned by roast_landing_page
confirmPaymentSpendNoSet to true only after the user has approved the $9 purchase. Without it this tool only quotes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint=false and openWorldHint=true, it discloses that step one charges nothing and creates no checkout session, that step two actually creates a Stripe checkout session and returns its URL, and that no account or card data is stored because payment happens on Stripe's page. These are exactly the side-effect details an agent needs before spending a user's money.

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?

Three tight sentences, front-loaded with the price and the two-step contract, then closed with the privacy/payment detail. Every sentence carries operational or trust-relevant information with no filler.

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?

With no output schema, the description still tells the agent what each call returns: a quote on the first, a checkout URL on the second. For a two-parameter purchase tool with annotations covering the safety profile, nothing an agent needs in order to call it correctly is missing.

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% and already explains that roast_id comes from roast_landing_page and that confirmPaymentSpend without approval yields a quote only. The description reinforces the consent framing but adds no syntax or format meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: quote and buy the $9 full teardown for a roast, and it makes the two-phase nature explicit. It never names the sibling get_full_teardown, however, so an agent must infer the read-vs-purchase split from the names alone.

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

Usage Guidelines5/5

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

It spells out the exact call sequence: first call with only roast_id to get a quote, then call again with confirmPaymentSpend: true only after the user has said yes. The precondition (explicit user approval) and the no-charge guarantee on the first call are both stated, leaving nothing to inference.

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