Skip to main content
Glama

List every text model and price

list_models
Read-onlyIdempotent

Every chat, embedding, rerank and transcription model on RelaySwitch with its id, type, the routes and tools that take it, our price (per million tokens, or per audio minute for transcription), the developer's list price where recorded, the wire formats it answers (openai, anthropic, gemini) and its specs. Image, video, speech, music and 3D models are in list_media_models. No key needed. Live from GET /v1/catalog.

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
typeNoOnly models of this type. Default: every text model.
searchNoA substring of the model id or name (opus, deepseek, uncensored...).
developerNoOnly models from this developer (Anthropic, OpenAI, Google, DeepSeek...).

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?

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing data freshness ("Live from GET /v1/catalog") and that no key is required. It also enumerates the return payload's contents, though it says nothing about result volume or pagination for a catalog that could be large.

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?

Front-loaded with the scope of the listing, followed by the sibling exclusion and the auth note — every element is load-bearing. The first sentence is a long comma-chained list of returned fields, which is dense but still readable.

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?

With no output schema, the description carries the burden well by enumerating returned attributes (id, type, routes, price currency basis, wire formats, specs). The main omission is any indication of catalog size or whether results are paginated.

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% and the enum for type is documented, so the baseline is 3. The description's pricing and wire-format detail pertains to outputs rather than the three filters, so it adds no parameter meaning beyond the schema.

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 resource (every chat, embedding, rerank and transcription model) with the fields returned (id, type, routes, price, wire formats, specs), and explicitly excludes media models by naming list_media_models. An agent can distinguish it from siblings without opening the schema.

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?

Gives a clear routing rule: text models here, image/video/speech/music/3D in list_media_models. It also clarifies there is no auth prerequisite ("No key needed"), which is genuine usage context. It stops short of explicit when-not-to-use guidance for model lookups that could also go through search-style siblings.

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.