Skip to main content
Glama

get_full_teardown

Read-only

Read the paid $9 full teardown for a roast, as Markdown. While it is unpaid it returns the free roast and says how to buy it; for the minute after payment it says it is still being written; then it returns the full teardown.

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

Input Schema

NameRequiredDescriptionDefault
roast_idYesThe roast_id returned by roast_landing_page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and closed-world; the description adds the substantive behavior the agent can't get elsewhere: the $9 paywall, the three-state return machine including a post-payment write lag, and the Markdown output format. This is exactly the additive context the annotations don't cover.

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?

Front-loads the core purpose, then packs the state machine into one compact semicolon-chained sentence with no wasted words. Slightly dense to parse in a single pass, which keeps it off a 5.

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 carries the burden of describing returns and does so for all three lifecycle states, including the transient 'being written' case an agent would otherwise mishandle. Nothing needed 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 coverage is 100% and the single roast_id param is already documented as coming from roast_landing_page, so the schema does the work. The description adds no further meaning (no format, no validation, no error behavior for unknown ids), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read the paid $9 full teardown for a roast") plus the return format (Markdown), which separates it from buy_full_teardown (purchase) and roast_landing_page (entry point) without needing their schemas.

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?

Describes the call's outcomes by payment state — unpaid returns the free roast with purchase instructions, the minute after payment returns a 'still being written' notice, then the full teardown — which implicitly routes the agent to buy_full_teardown when it lacks entitlement. No explicit 'use X instead of Y' sentence, so short of a 5.

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