Skip to main content
Glama

List every text model and price

list_models
Read-onlyIdempotent

Every chat, embedding, rerank and transcription model on UncensoredLLM 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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is supplied. The description adds genuine context beyond them: no authentication required, and the data is live from GET /v1/catalog so results reflect the current catalog. It also discloses the pricing units (per million tokens, per audio minute) and hedges that the developer list price is only 'where recorded,' which warns the agent about possibly missing values.

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?

Two sentences, front-loaded with what is returned, followed by the alternative and then the auth/freshness notes. The long enumeration of returned fields is dense but each element is informative. Minor density cost, no filler sentences.

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?

With no output schema, the description carries the burden of return-value disclosure and does so by enumerating the fields the agent will receive, including price units and wire formats. Scope, sibling boundary, authentication and data freshness are all covered, leaving nothing an agent needs in order to call it 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%, and all three filters (type, search, developer) are documented in the schema with examples and an enum on type. The description only implies type filtering by naming the model categories and adds no syntax or default behavior beyond what the schema already states, so the baseline of 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 (list) and a precisely bounded resource (every chat, embedding, rerank and transcription model on UncensoredLLM), then enumerates the returned fields including id, type, routes, pricing, wire formats and specs. It explicitly contrasts with list_media_models, so an agent can separate text-model listing from media-model listing 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 Guidelines4/5

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

The boundary with alternatives is stated outright: 'Image, video, speech, music and 3D models are in list_media_models,' which tells the agent exactly when to route elsewhere. It also clarifies 'No key needed,' indicating unauthenticated calls are fine. There is no further guidance on when to prefer this over media_model or estimate, but the primary exclusion is handled well.

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.