Skip to main content
Glama

List every text model and price

list_models
Read-onlyIdempotent

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them: no authentication required, and the data is live from GET /v1/catalog rather than cached, which tells the agent results are fresh. It stops short of stating pagination or result-size limits, but no limit parameters exist to imply them.

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 sentence, followed by two short routing and freshness sentences — no filler. The opening enumeration of returned fields is dense and runs long as a single sentence, but every element is informative rather than redundant.

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?

There is no output schema, so the description carries the burden of describing returns, and it does: id, type, routes/tools, price with units, developer list price, wire formats, and specs. Combined with the sibling routing and the auth note, an agent has everything needed to select and call this tool correctly.

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 parameters (type, search, developer) are already documented in the schema with enum values and examples; baseline is 3. The description adds only the pricing-unit nuance (per million tokens vs per audio minute for transcription), which is return-value semantics rather than input guidance.

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 (list every text model) and enumerates the exact scope: chat, embedding, rerank and transcription. It also names the sibling that holds the rest (list_media_models), so an agent can distinguish this tool from its closest neighbor without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the excluded categories — image, video, speech, music, 3D — to list_media_models, which is the one real selection decision for this family of tools. It also states 'No key needed,' removing a prerequisite question that would otherwise require a trial call.

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.