Skip to main content
Glama

Cheapest input price per model

cheapest
Read-onlyIdempotent

Models ordered by their lowest input price on any channel, with the channel that offers it. Optional vendor or channel kind (OFFICIAL, CLOUD, AGGREGATOR). List prices as published by each channel at observed_at, USD per 1M tokens unless stated; China-site price lists are in CNY, listed separately and never converted. Standard (on-demand) plan unless service_plan says otherwise. The channel's own page is authoritative. Aggregator prices are the marketplace's own and never the reference. A missing price is unknown, not free. Not purchasing advice.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
vendorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, yet the description adds substantial pricing semantics: USD per 1M tokens, China-site CNY lists kept separate and never converted, standard on-demand plan default, channel page is authoritative, aggregator prices are not the reference, and missing prices mean unknown rather than free. It stops short of describing output fields or pagination beyond the limit cap.

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 core output is front-loaded in the first sentence and the semantic caveats follow in compact clauses. A few trailing statements (authoritative source, not purchasing advice) are arguably peripheral but short enough to earn their place as disambiguation.

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

Completeness4/5

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

For a read-only ranking with no output schema and only optional filters, the description covers the result content (model, price, channel) and the caveats that would otherwise cause misreading. The only real gap is the undocumented limit parameter and no note on ordering ties or result count.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry all parameter meaning. It explains vendor and elaborates the kind enum (OFFICIAL, CLOUD, AGGREGATOR), but never mentions the limit parameter or its 1-50 range, leaving one of three parameters undocumented.

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: models ordered by lowest input price per channel, including the winning channel. That distinguishes it from a plain price lookup like check_price or get_price, though it never names a sibling or explicitly contrasts with compare_channels.

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?

The optional vendor and kind filters are framed as narrowing the cheapest-price ranking, which implies the use case, but there is no explicit when-to-use or when-to-prefer-an-alternative statement (e.g. vs compare_channels or price_index).

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.