Skip to main content
Glama

List models

list_models
Read-onlyIdempotent

List supported generation models in Rainbrand’s public API. Filter by output type or search query. Returns each model's ID, provider, name, output type, capabilities, and description.

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
typeNoOutput medium the model should produce. Omit to browse all supported model types.
limitNoNumber of models to include in this page of results.
queryNoSearch for a model by name or description.
cursorNoPass next_cursor from the previous result to get the next page.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
modelsYesModels on this page.
has_moreYesWhether more results follow this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a summary of returned fields (ID, provider, name, output type, capabilities, description), but that duplicates the existing output schema rather than disclosing pagination limits, rate limits, or catalog recency.

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?

Three short sentences, front-loaded with the core action, with no filler beyond the mild framing phrase 'in Rainbrand's public API.' Nothing is wasted, but the return-value sentence is redundant given the output schema.

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 a full output schema, rich annotations, and 100% parameter description coverage, an agent has everything needed to call this tool correctly. The description is appropriately scoped for a simple read-only listing operation.

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 the baseline is 3. The description reinforces the meaning of the type and query filters but says nothing about limit, cursor, or the analytics-only llm_model parameter, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: 'List supported generation models in Rainbrand's public API,' plus filtering capability. It is clearly distinct from content-listing siblings such as list_images or list_videos, though it never names an alternative to differentiate itself.

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

Usage Guidelines3/5

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

'Filter by output type or search query' implies the browsing use case, and the schema's enum description says to omit type to browse all. There is no explicit when-to-use or when-not-to-use guidance and no named alternative tool.

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