Skip to main content
Glama

Agent Exchange store

models_cheapest

$0.002 via x402: The cheapest models that fit a job: rank by blended price (3 parts prompt, 1 part completion) under constraints min_context=, modality= (image, file, audio), reasoning=true, provider=, exclude_free=true (default; free routes are rate-limited); top= (default 10). Pay 0.002 USDC through https://store.agentexchange.work/gw/models/cheapest?min_context=128000&modality=image Via the Agent Exchange store

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": "models_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNotop
modalityNomodality
providerNoprovider
reasoningNoreasoning
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)
min_contextNomin_context
exclude_freeNoexclude_free

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?

No annotations exist, so the description carries the full burden, and it does disclose meaningful behavior: the tool is paid ($0.002 USDC via x402), the ranking formula's weighting, and that free routes are rate-limited. It omits what the response looks like, how unpaid calls behave beyond the price, and pagination for top, leaving some gaps for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loads the price, but the middle is a run-on clause chain mixing ranking logic, filters, and payment instructions, and the long example URL is embedded awkwardly. Every fragment is informative, yet the structure makes it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, zero annotations, and no output schema, the description should carry more: it never describes the return shape, ordering guarantees for the ranking, or behavior when x_payment is absent or invalid beyond mentioning the price. It covers the input side adequately but leaves the response and payment-failure behavior underspecified.

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 nominally 100% but the schema's own descriptions are just the parameter names repeated, so real meaning comes from the description: modality values (image, file, audio), top default 10, exclude_free default and consequence, and a concrete min_context example (128000). It adds genuine semantics beyond the schema, though reasoning and provider values are left unenumerated.

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 verb and resource — ranking models by blended price (3:1 prompt/completion) subject to filters — which is concrete and clearly distinct from sibling catalogue tools like models_models or models_model. An agent knows exactly what output category to expect: a cheapest-fit model list.

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?

Supplies the operative constraints (min_context, modality, reasoning, provider), the defaults (exclude_free=true, top=10), and the rationale for the default ('free routes are rate-limited'), giving clear context for when this tool fits a selection task. It never names the alternative sibling (e.g. models_models) or says when not to use it, so it falls short of explicit routing.

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