Skip to main content
Glama

List models in the Token Price Index

list_models
Read-onlyIdempotent

Models with their official input/output list price, lowest channel and page. Optional vendor id or free-text filter. 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": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text: model name, id or alias
vendorNoVendor id: anthropic, openai, google, meta, deepseek, alibaba, moonshot, zhipu, minimax

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?

With annotations already covering read-only/idempotent/no-destruction, the description still adds substantial domain context: prices are as published at observed_at, China-site lists are CNY and never converted, standard on-demand plan applies unless service_plan says otherwise, the channel page outranks aggregators, and a missing price is unknown rather than free. It omits pagination mechanics despite mentioning 'page'.

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 payload description is front-loaded in sentence one and each subsequent clause carries a distinct caveat, so nothing is filler. The telegraphic, verbless phrasing of the first sentence costs a little clarity.

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 two-parameter, read-only browse tool with no output schema, the description predicts the returned fields (input/output price, lowest channel, page) and explains price semantics and currency rules. Only pagination behavior and how 'lowest channel' is chosen remain unexplained.

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 100%, so 'q' (name/id/alias) and 'vendor' (with enumerated vendor ids in the schema description) are already fully documented; the description's 'Optional vendor id or free-text filter' merely restates them without adding matching or syntax semantics. Baseline 3 applies.

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?

The opening sentence names the resource (models) and the payload it returns ('official input/output list price, lowest channel and page'), which is specific enough to separate it from check_price or cheapest, though it is a verbless fragment rather than an explicit 'list all models' statement.

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 description implies a browse/enumerate use case via 'Optional vendor id or free-text filter' but never states when to pick this over siblings such as check_price, cheapest, or compare_channels; the remaining sentences are data-interpretation caveats, not routing guidance.

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.