Skip to main content
Glama

Browse models

list_models
Read-onlyIdempotent

List every available generation model in the catalog with its category, parameters and defaults, which params take uploaded files, and a default-request estimate labelled by price_basis (default_request, input_dependent, or duration_ceiling): cost_credits is what the call bills in whole app credits ($0.10 each), and cost_micros/cost_usd are the same amount in usd_micros and USD. Call this first to discover valid model values and how to price/shape a run call.

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
allNoset true to search the FULL sellable catalog instead of just the featured set. Results are still paged - read total and use offset
limitNohow many models to return (default 50, max 200). The catalog is over a thousand models, so page rather than fetching everything
offsetNohow many matches to skip, for paging through total
searchNocase-insensitive substring matched against the model name and description, e.g. "upscale" or "kling"
compactNoset true while shopping: omits each model's params and shortens its description, so a page costs a fraction of the tokens. Fetch the full entry for the one model you settle on
categoryNooptional category filter, e.g. text-to-image, image-to-video, text-to-speech, speech-to-text
max_creditsNofilter by the displayed default-request estimate, which may be an input fallback or duration ceiling; not a run spending cap
include_variableNowith max_credits, also include input-dependent and variable-duration estimates above that budget. Their actual costs may be lower OR higher; this is discovery, not a spending guarantee.

Output Schema

NameRequiredDescriptionDefault
noteYes
totalYes
modelsYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive browse, so the safety profile is covered. Beyond that, the description adds real behavioral context: the price_basis labelling scheme, the meaning and unit of cost_credits ($0.10 each) versus cost_micros/cost_usd, and the token-saving compact mode. It does not restate pagination limits or ordering of results, keeping it short of a 5.

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?

It is front-loaded with the core action and the 'call this first' directive lands early; density is high and most clauses earn their place. The cost/credits sentence is somewhat long and packs three field names plus a unit conversion, which slightly dilutes scannability but is not wasteful.

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 discovery tool with an output schema, rich annotations, and fully documented parameters, the description covers what an agent needs: what it returns, how to price results, and when to call it before run. The remaining gap is minor — it does not describe result ordering or how featured versus full-catalog pagination differ in practice.

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 eight parameters already carry their own explanations and the baseline is 3. The description reinforces the price_basis and cost_credits semantics, which is mostly return-value context already implied by the output schema, so it does not materially deepen 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?

The description opens with a specific verb and resource ('List every available generation model in the catalog') and immediately scopes what each entry contains: category, parameters and defaults, file-taking params, and a default-request price estimate. That is clearly distinguishable from siblings such as run, balance, or get_job, which are actions rather than catalog browsing.

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?

It gives an explicit when-to-use: 'Call this first to discover valid `model` values and how to price/shape a run call,' which ties it to the run workflow. It also gives paging guidance (read total, use offset) via the schema, but it stops short of naming a when-not or a direct alternative, so the routing picture is clear rather than exhaustive.

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