Skip to main content
Glama

Preview changes to a saved search

quote_edit_preview
Idempotent

Quote a preview of an alert with some settings changed. Poacher covers it, so nothing is charged. Anything you leave out is copied exactly. Does not change the alert. Approve with approve_preview; applying the change later is a separate update.

Permission: work:execute + alerts:read.

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": {
      "alert_id": "<alert_id>",
      "configuration_revision": "<configuration_revision>",
      "idempotency_key": "<idempotency_key>",
      "changes": "<changes>"
    },
    "name": "quote_edit_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYesOnly the settings to change.
alert_idYesAlert ID.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.
maximum_charge_microsNoOptional and ignored while Poacher covers previews. If you send it, use a whole number of at least 2 micros.
configuration_revisionYesconfiguration_revision from get_alert_configuration.

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: -"Ceiling in USD micros."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: -[
      -  "alert_id",
      -  "configuration_revision",
      -  "maximum_charge_micros",
      -  "idempotency_key",
      -  "changes"
      -]New value: +[
      +  "alert_id",
      +  "configuration_revision",
      +  "idempotency_key",
      +  "changes"
      +]
    • 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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false; the description adds the key behavioral facts beyond them — no charge is incurred, the alert itself is untouched, and omitted settings are copied verbatim. It also discloses the permission requirements. Minor gap: it doesn't say whether a preview expires or how long it stays approvable.

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?

The purpose and the no-charge/no-change guarantees are front-loaded and each sentence carries distinct information. The phrasing is slightly scattered — 'Poacher covers it' is idiosyncratic and the approve/update sentence could be tightened — but there is no filler.

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?

For a 5-parameter nested-schema tool with an output schema and full annotations, the description covers purpose, cost, mutation scope, patch semantics, the follow-up action, and permissions. The output schema relieves it of explaining the returned quote, so little an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining patch semantics ('Anything you leave out is copied exactly') and by explaining why maximum_charge_micros is inert ('Poacher covers it, so nothing is charged'), which the schema only states as 'ignored'. It doesn't explain configuration_revision staleness, which is the main failure mode.

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

Purpose4/5

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

The verb and resource are specific: quoting a preview of an alert with changed settings, plus the explicit scope statement 'Does not change the alert.' That separates it from edit_alert and the approve_* family, though it never distinguishes itself from quote_preview, which an agent could easily confuse it with.

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?

It gives a clear workflow context and next step: 'Approve with approve_preview; applying the change later is a separate update,' which tells the agent this is a non-terminal, pre-approval step. It stops short of stating when to prefer this over quote_preview or edit_alert directly, so it is clear but not exhaustive.

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