Skip to main content
Glama

list_models

Read-onlyIdempotent

Paid models in today's OpenRouter catalogue with list prices in USD per million tokens. Filter by lab or price.

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
labNoOptional lab or model words, for example "qwen" or "deepseek"
limitNoMax results, default 25, max 100
max_input_priceNoOptional max input price, USD per million tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results are scoped to 'paid models' (free models are excluded), reflect 'today's' catalogue (freshness), and prices are normalized to USD per million tokens. It stops short of describing ordering or pagination behavior.

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

Conciseness5/5

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

Two short sentences, zero filler, and the scope/units constraint is front-loaded before the filtering capability. Every clause carries information.

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 simple, read-only, zero-required-parameter listing tool with a fully documented schema and no output schema, the description covers scope, units and filtering adequately. Minor gaps remain: no mention of the default result limit or of which price fields (input vs. output) appear in the response.

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 description coverage is 100%, so the schema already documents lab, limit and max_input_price. The description only echoes that filtering is possible by lab or price and adds no syntax, matching behavior, or interaction detail (e.g., whether lab matches model names, or that only input price is filterable). Baseline 3 is appropriate.

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 description names a specific resource and scope: paid models from today's OpenRouter catalogue, with list prices in USD per million tokens. That is far more informative than the bare tool name, but it does not explicitly distinguish itself from the sibling cost_estimate, leaving the agent to infer the catalogue-listing vs. cost-computation split.

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?

"Filter by lab or price" implies the browsing use case, but there is no explicit statement of when to choose this over cost_estimate, nor any exclusion such as 'do not use this to compute actual spend'. Usage is only implied.

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