Skip to main content
Glama

Quote a preview

quote_preview
Idempotent

Set up a one-time preview of what an alert would find: one url, or sources (1–10 search URLs) each with its own interval and schedule, plus shared criteria. Poacher covers previews for now, so no ceiling is needed and nothing is charged. Saves a quote only; nothing runs yet. Returns request_hash for approve_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": {
      "criteria": "<criteria>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOne public search URL. Use url or sources, not both.
nameNoName for the preview.
sourcesNo1–10 distinct search URLs. Put interval_seconds and schedule on each source, not at the top level.
criteriaYesWhat counts as a match, in plain words.
scheduleNoWith url only: phase for checks.
review_resultsNoDefault true: Poacher reviews each result against the criteria. false checks exact filters only.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.
interval_secondsNoWith url only: check interval.
maximum_charge_microsNoOptional and ignored while Poacher covers previews. If you send it, use a whole number of at least 2 micros.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / maximum_charge_micros / description
      Previous value: -"The most the whole preview may cost, in USD micros. A ceiling, not an estimate. It must reach the minimum in `get_capabilities` (`paid_previews.minimum_charge_micros`); a lower one is refused with `ceiling_too_low`."New value: +"Optional and ignored while Poacher covers previews. If you send it, use a whole number of at least 2 micros."
    • changedInput schema / required
      Previous value: -[
      -  "criteria",
      -  "maximum_charge_micros",
      -  "idempotency_key"
      -]New value: +[
      +  "criteria",
      +  "idempotency_key"
      +]
    • 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. Changed4 schema fields changed
    • changedInput schema / properties / maximum_charge_micros / description
      Previous value: -"The most the whole preview may cost, in USD micros. A ceiling, not an estimate."New value: +"The most the whole preview may cost, in USD micros. A ceiling, not an estimate. It must reach the minimum in `get_capabilities` (`paid_previews.minimum_charge_micros`); a lower one is refused with `ceiling_too_low`."
    • 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.1/5.0
Behavior4/5

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

Annotations already cover readOnly=false, destructive=false, idempotent=true and openWorld=false, so the bar is lower. The description still adds real context: no execution occurs at quote time, nothing is charged and no ceiling is needed, the required permission is work:execute, and the response carries a request_hash. It leaves open how long a saved quote remains valid before approve_preview, which is the main remaining gap.

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 definition, then the two-mode input shape, then the no-charge/no-execution caveat, then the return value and permission. Every sentence carries information; the phrasing "Poacher covers previews for now" is slightly chatty but not wasteful.

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 9-parameter mutation tool with full schema coverage, an output schema and complete annotations, the description covers intent, side effects, permissions and the handoff to approve_preview. Missing only lifecycle details (quote expiry, what happens if criteria fail validation) that an agent might want before quoting.

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%, so the baseline is 3. The description adds only a light summary — that sources take their own interval_seconds and schedule while criteria is shared, and that max is 10 sources — all of which the schema already documents. Parameters like review_results, idempotency_key and maximum_charge_micros are not elaborated in prose.

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 action (set up a one-time preview of what an alert would find) plus the two shapes it accepts (one url, or 1–10 sources with per-source interval and schedule, plus shared criteria). It also distinguishes itself from full alert quoting by noting Poacher covers previews so nothing is charged, and it points to the downstream tool approve_preview.

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?

"Saves a quote only; nothing runs yet. Returns request_hash for approve_preview" makes the position in the workflow explicit: call this, then approve. It never states the negative case, e.g. when to prefer quote_alert_creation or quote_edit_preview instead, so the agent must infer the boundary from the preview/alert distinction.

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