Skip to main content
Glama

Run a quoted preview

approve_preview
Idempotent

Runs the quoted preview. Poacher covers its cost for now, so nothing is charged and the daily API allowance is not used. Never starts ongoing monitoring.

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>",
      "request_hash": "<request_hash>"
    },
    "name": "approve_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYesThe preview ID returned when it was quoted or created.
request_hashYesThe exact request_hash from the quote. Approval fails if anything changed since the quote.

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

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses concrete behavior: no charge is incurred, the daily API allowance is unaffected, and the call never starts ongoing monitoring. It also states the required permission scope (work:execute), which annotations do not convey. It does not say what becomes of the preview after approval or whether the approval can be replayed, leaving some lifecycle detail to the annotations.

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?

Three short sentences with the cost and scope caveats placed early, and the permission note kept as a compact footer. The opening sentence duplicates the title rather than adding information, which is the only real waste.

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 two-parameter, non-destructive, idempotent execution tool with an output schema, the description covers cost, allowance impact, permission, and the key negative guarantee about monitoring. The remaining gaps (post-approval preview state, failure modes) are minor given annotations and the output schema cover part of that ground.

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 both parameters carry descriptive text, so the schema already explains preview_id and request_hash. The description adds no further semantics such as how the hash is computed or what error surfaces on mismatch, so baseline 3 applies.

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

Purpose3/5

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

The opening line 'Runs the quoted preview' largely restates the title and only loosely specifies the action (executing a previously quoted request), without naming the flow (quote -> approve -> result) that would distinguish it from approve_check or approve_monitoring. The added clause 'Never starts ongoing monitoring' does help scope the effect, but the core purpose sentence is close to tautology.

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?

There is no explicit 'use this when' guidance or named alternative, so an agent has to infer that this is the step after quote_preview from the phrase 'quoted preview' and the required preview_id/request_hash. The negative scoping 'Never starts ongoing monitoring' implicitly separates it from approve_monitoring, which is useful but indirect.

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