Skip to main content
Glama

Quote for a whole stack

stack_quote

One call, the best current answer for a whole stack: a list of items (kind vps: vcpu, ram_gb, disk_gb, region, term, currency, count; kind gpu: gpu, count, hours_per_month, region, gpus_per_instance; kind llm or inference: model, input_mtok, output_mtok, count). Per item the 5 cheapest offers with a verified price (the free ordering: price only, nothing for money), the monthly cost for your count and usage (a stated unit price times your quantities, nothing estimated), verified_at, source_url and a scope line; an item with no fresh match says so. Totals per currency, never converted. Same answer as POST /v1/quote. Free: 3 quotes a day per address; beyond that 1 credit per quote on an API key (see /pricing). Reads prices, and records the free quote or credit it uses (so it is not read-only). Pass an idempotency_key to retry without a second charge. Returns an error object (HTTP 402 body) when out of credits.

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": {
      "items": "<items>"
    },
    "name": "stack_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYese.g. [{"kind":"vps","vcpu":4,"ram_gb":8,"region":"eu","term":"any","count":3},{"kind":"gpu","gpu":"H100","count":1,"hours_per_month":200},{"kind":"llm","model":"gpt-5","input_mtok":50,"output_mtok":10}]
idempotency_keyNo1 to 128 characters; the same key never charges twice (API key callers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Strong disclosure beyond the annotations: it explains why readOnlyHint=false ('records the free quote or credit it uses'), the credit/rate model, the per-item result shape (5 cheapest verified offers, verified_at, source_url, scope line), 'nothing estimated', totals never converted, and a 402 error body. The idempotency note is consistent with idempotentHint=false – the tool is not inherently idempotent, a key is required – though the description does not spell out that distinction.

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 one-line value proposition, then proceeds to result shape, cost model, and limits in a defensible order with no filler sentences. It is dense and parenthetical-heavy, approaching a run-on, but nearly every clause carries decision-relevant information.

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 two-param batch-pricing tool with no output schema, the description covers what comes back (per-item offers, monthly cost computation, totals per currency, no-match signaling), failure behavior (402 out-of-credit body), and billing implications. Nothing an agent needs to call it correctly or interpret the result is missing.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description still adds meaning: it names the exact per-kind fields (vps: vcpu, ram_gb, disk_gb, region, term, currency, count; gpu: gpu, count, hours_per_month, region, gpus_per_instance; llm: model, input_mtok, output_mtok, count) for an items array the schema types only as a free-form object with a single example. The idempotency_key retry semantics are also restated in context of charging.

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?

States a specific verb and resource with scope: 'the best current answer for a whole stack: a list of items', and enumerates the three item kinds (vps, gpu, llm/inference) it can quote. The multi-item 'whole stack' framing implicitly separates it from single-lookup siblings like get_price or cheapest_for_spec, but no sibling is named, so the differentiation is inferred rather than stated.

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?

Usage is implied by the batch framing and by concrete operational notes (3 free quotes/day per address, 1 credit beyond that, pass an idempotency_key to avoid a second charge). What is missing is selection guidance: nothing says when to use this instead of estimate_cost, get_price, or cheapest_for_spec for a single SKU, nor any exclusions.

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