Skip to main content
Glama

Quote a one-off check

quote_check
Idempotent

Set a spending ceiling for checking one active alert once now: all its sources plus result review. Saves a quote only; nothing runs and nothing is charged. Returns request_hash for approve_check.

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": {
      "alert_id": "<alert_id>",
      "maximum_charge_micros": "<maximum_charge_micros>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesActive alert ID.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.
maximum_charge_microsYesThe most this check may cost, in USD micros (1,000,000 micros = 1 USD). A ceiling, not an estimate.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maximum_charge_micros / description
      Previous value: -"The most this check may cost, in USD micros (1,000,000 = $1). A ceiling, not an estimate."New value: +"The most this check may cost, in USD micros (1,000,000 micros = 1 USD). A ceiling, not an estimate."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the critical side effect: it only saves a quote, nothing runs, and nothing is charged. It also names the permission (work:execute) and the returned request_hash needed for approval. It does not cover quote validity or expiry, but the safety-relevant behavior is well communicated.

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?

The description is four short sentences with no waste, and the core action and no-charge guarantee are front-loaded. Every sentence adds useful information: scope, side effect, next step, and permission.

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?

Given the three-parameter schema, annotations, and output schema, the description provides enough context to call the tool correctly and understand its place in the approval workflow. It covers purpose, side effects, permission, and the returned request_hash without needing to restate schema details.

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 parameters are already well documented. The description still adds meaning by explaining that the spending ceiling covers checking all sources plus result review, which clarifies the scope of maximum_charge_micros beyond the schema text.

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?

The description uses a specific verb and resource: set a spending ceiling to quote checking one active alert once, covering all sources plus result review. It also clarifies that the tool only saves a quote and returns a request_hash for approve_check, which cleanly separates it from the approval step.

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 clear usage context: quote a one-off check for one active alert now, then pass the returned request_hash to approve_check. It does not explicitly state when not to use it or name a separate alternative, but the workflow and scope are easy to infer.

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