Skip to main content
Glama

Cheapest for a spec

cheapest_for_spec
Read-onlyIdempotent

Cheapest active SKUs meeting a minimum spec, ranked by list price only (no sponsorship, no affiliate weighting), excl. VAT (VAT-inclusive plans are ranked after removing their stated VAT rate; rank.vat_basis says so). gpu and vps default to commitment=on-demand: spot, reserved, committed, dynamic and community-cloud prices are left out unless commitment says otherwise. category vps|gpu|llm; vcpu, ram_gb, disk_gb minimums; gpu model substring (e.g. H100; with a memory size such as A100-80GB the card must state exactly that memory); region 'eu' for EU-deployable; currency USD|EUR for the ranking. Each row carries verified_at, stale and source_url. coverage_gaps names the providers not read yet (for vps: those still named in the answer), so a floor is never mistaken for the whole market.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cheapest_for_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuNoGPU model substring, e.g. H100
vcpuNoMinimum vCPUs
limitNoMaximum rows, 1 to 50
ram_gbNoMinimum RAM in GB
regionNo'eu' for EU-deployable, 'us', 'asia', a country code such as nl or de (the places of the compare page), or a provider region code
disk_gbNoMinimum disk in GB
listingNoListing filter, default current: only plans on the provider's public price page or product API count. all includes catalog-only and vanished plans (each row carries listing_status).current
categoryNovps, gpu or llmvps
currencyNoUSD or EUR (ranking currency)USD
providerNoProvider slug to restrict to
gpu_countNoMinimum GPUs per instance
commitmentNogpu and vps only. Default on-demand: standing list prices with no term and no interruption. spot, reserved, commit, dynamic or community select those rows; any shows every commitment (each row carries extra.commitment).on-demand
include_staleNoAlso rank plans whose price is not verified (stale): after every current one, each flagged stale. Off by default.
include_region_unstatedNovps with a region filter only. A plan whose source states no region is never guessed into the place: it is left out of the rows, counted in region_unstated (count, and the cheapest of them). 1 = rank those plans with the others (the compare page's region_unknown=1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish a safe read-only, idempotent, non-destructive operation. The description adds substantial behavioral context: VAT normalization, ranking exclusions, commitment defaults, stale handling, verified_at/source_url on each row, and coverage_gaps to avoid mistaking a floor for the whole market.

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 description is dense and front-loads the core purpose and ranking rule before moving into defaults and caveats. It is long but largely justified for a 14-parameter tool, though some parenthetical clauses could be split for easier scanning.

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 tool's complexity, 14 optional parameters, and absence of an output schema, the description is complete: it explains ranking logic, defaults, exclusions, returned row fields, stale-plan comments, and coverage_gaps. An agent has enough context to invoke it accurately and interpret the result boundaries.

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 input schema already explains most parameters. The description still adds meaningful semantics beyond the schema, especially exact GPU memory matching (A100-80GB), VAT-inclusive price normalization, commitment default behavior, and the distinction between list price ranking and sponsorship/affiliate weighting.

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 names a specific verb and resource: finding the cheapest active SKUs that meet a minimum spec, ranked by list price. It immediately clarifies the ranking basis (list price only, no sponsorship or affiliate weighting), which distinguishes it from a generic SKU search.

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 conditions: gpu and vps default to on-demand, spot/reserved/committed/dynamic/community prices are excluded unless requested, and region/category constraints are explained. It does not explicitly name sibling alternatives such as search_skus or get_price, so the when-to-use-vs-alternative guidance is implied rather than stated.

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