Skip to main content
Glama

Stop a preview

cancel_preview
DestructiveIdempotent

Stop further paid steps of a preview. Work already sent can finish and is charged. Safe to repeat.

Permission: work:execute.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "cancel_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYesThe preview ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedOutput schema / properties / data / properties / covered_by_poacher
      Added value: +{
      +  "description": "True when Poacher covers this preview: nothing is charged. Set when the preview is quoted and kept for its life.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / data / properties / minimum_charge_micros / description
      Previous value: -"The smallest maximum_charge_micros this preview accepts: enough for every setup step to reserve its most expensive case. You are charged actual cost, usually far less."New value: +"The smallest maximum_charge_micros this preview accepts: enough for every setup step to reserve its most expensive case. You are charged actual cost, usually far less. 0 while Poacher covers the preview."
    • removedOutput schema / properties / data / properties / quote / properties / charge_unsuccessful_work / description
      Removed value: -"Always true."
    • addedOutput schema / properties / data / properties / quote / properties / charge_unsuccessful_work / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • addedOutput schema / properties / data / properties / quote / properties / covered_by_poacher
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / data / properties / quote / properties / gross_margin_bps / description
      Previous value: -"Always 5000."New value: +"One of: 0, 5000."
    • changedOutput schema / properties / data / properties / quote / properties / maximum_charge_micros / description
      Previous value: -"USD micros as an exact integer; 1,000,000 = $1. Spending ceilings are bounded to the safe integer range."New value: +"0 while Poacher covers the preview."
    • addedOutput schema / properties / data / properties / receipt / properties / covered_by_poacher
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / data / properties / receipt / properties / maximum_charge_micros / description
      Previous value: -"The ceiling for the whole preview, across answered rounds."New value: +"The ceiling for the whole preview, across answered rounds. 0 for a covered preview."
    • addedOutput schema / properties / data / properties / receipt / properties / provider_cost_micros / description
      Added value: +"What the account pays toward provider costs. 0 for a covered preview."
    • changedOutput schema / properties / data / properties / receipt / properties / status / description
      Previous value: -"One of: \"not_started\", \"pending\", \"final\"."New value: +"covered: Poacher pays for this preview, so charged_micros is always 0. One of: \"not_started\", \"pending\", \"final\", \"covered\"."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / data / properties / answered_rounds
      Added value: +{
      +  "description": "How many times this preview’s clarification questions have been answered.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / data / properties / minimum_charge_micros
      Added value: +{
      +  "description": "The smallest maximum_charge_micros this preview accepts: enough for every setup step to reserve its most expensive case. You are charged actual cost, usually far less.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / data / properties / receipt / properties / maximum_charge_micros / description
      Previous value: -"USD micros as an exact integer; 1,000,000 = $1. Spending ceilings are bounded to the safe integer range."New value: +"The ceiling for the whole preview, across answered rounds."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds two things they do not: the partial-effect semantics (in-flight work still completes and is still billed) and the required permission work:execute. Only the "safe to repeat" line is redundant with idempotentHint.

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 short sentences plus a permission line, with the core behavior and its billing caveat front-loaded. Nothing is padded, and each line carries a distinct fact.

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?

An output schema exists, so return values need not be described, and the description covers billing side effects, idempotency, and authorization for a destructive one-parameter tool. It stops short of covering post-completion states or error conditions, which is a minor gap.

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 preview_id parameter is fully documented in the schema, including its format and origin. The description adds no further meaning about that parameter, so the baseline of 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?

"Stop further paid steps of a preview" names a specific verb (stop), a specific resource (preview), and a precise scope (further paid steps only). That scope wording separates it from siblings like approve_preview or get_preview without needing to name 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 description implies when to call it (to halt remaining billable work on a preview) and adds a reassurance about repeat calls, but it never states when not to use it or points to an alternative such as approve_preview or get_preview. An agent must infer the routing decision.

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