Skip to main content
Glama

Answer a preview’s questions

answer_preview_questions
Idempotent

When a preview’s status is needs_clarification, ask the person its questions and send their answers here, one per question in the order asked. The same preview continues. Poacher covers it, so there is no new quote, approval or charge. Use the key that quoted the preview.

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>",
      "answers": "<answers>"
    },
    "name": "answer_preview_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesThe person’s answers, one per question, in the order asked.
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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it non-destructive, idempotent and open-world, but the description adds genuinely new context: the same preview continues, no new quote/approval/charge is incurred, and the work:execute permission is required. It does not state what happens on a wrong number of answers or whether the status changes afterward, which keeps it off a 5.

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-loaded with the triggering condition, then the cost reassurance, then the permission. Three compact sentences with no filler; the only rough edge is 'Poacher covers it', which reads as internal shorthand and is less clear than the following clause.

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?

A two-parameter, low-complexity tool with a full output schema present, so return values need not be described. The description supplies the precondition, the ordering contract, the cost model and the permission scope, leaving nothing an agent needs in order to invoke it correctly.

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 fields are already documented, including the ordering rule and the 1-3 item bounds. The description only restates the ordering convention and adds the ambiguous hint 'use the key that quoted the preview', which does not clearly map to preview_id or to an auth key.

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?

Names a specific action (send answers to a preview's questions) tied to a concrete precondition (status is needs_clarification) and to a specific resource (the preview, identified by preview_id). An agent can distinguish it from approve_preview, cancel_preview, or quote_preview purely from this sentence.

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?

The trigger is explicit: use it only when the preview's status is needs_clarification, and use the same key that quoted the preview. It does not enumerate the alternative actions (approve, cancel) by name or say what to do if no questions were asked, so it stops short of a full routing rule.

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