Skip to main content
Glama

List every text model and price

list_models
Read-onlyIdempotent

Every chat, embedding, rerank and transcription model on UplinkSwitch 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.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: no authentication required, results are live from GET /v1/catalog, and it discloses the shape of returned records including the price unit (per million tokens, or per audio minute for transcription). Pagination or result-size behavior is not mentioned.

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 main payload — what is returned — is front-loaded in the first sentence, followed by the media-model routing, then two short facts (no key, live endpoint). It is dense but every clause carries information; the record-field enumeration is long yet justified because there is no output schema.

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

Completeness5/5

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

For a three-filter, zero-required-parameter catalog listing with no output schema, the description covers what the tool returns, the units of the price field, the auth requirement, the data source, and where the non-covered model classes live. Nothing an agent needs in order to call it correctly appears to be missing.

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 all three filters (type, search, developer) are already documented in the schema, including the enum values and default. The description's enumeration of the four text model types reinforces the type enum but adds no new filtering semantics. Baseline 3 applies.

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: it enumerates every chat, embedding, rerank and transcription model, and lists exactly what each record carries (id, type, routes, price, wire formats, specs). It also explicitly names the sibling that covers the excluded model classes, so an agent can distinguish it from list_media_models without opening either 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: image, video, speech, music and 3D models live in list_media_models, and no key is needed here. It stops short of stating when to prefer this catalog call over the search/compare siblings, so the exclusions are covered but the full alternative space is not.

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.