Skip to main content
Glama

List models

list_models
Read-only

List the models you can generate with. Filter by feature slug (e.g. image-generation, image-editing, text-to-video, image-to-video, lipsync, text-to-speech), output_type (image | video | audio) or a query substring. Prices are credits.

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
queryNo
featureNo
output_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds a genuinely useful behavioral detail — that prices are expressed in credits — but says nothing about whether results are workspace-scoped or how large the list can be.

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 purpose, then the three filters in a single compact sentence. The long parenthetical slug list is dense but every entry is informative for a filter that accepts arbitrary feature strings.

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?

Three optional parameters are all explained, and an output schema exists so return values need no prose. The main residual gap is what happens when no filters are supplied and whether the model set is account- or workspace-specific.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameters, and it does: feature is explained with concrete slug examples (image-generation, lipsync, text-to-speech), output_type is given its value set (image | video | audio), and query is described as a substring match. Only the defaults/empty behavior are left implicit.

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 specific verb and resource ('List the models you can generate with'), which separates it from siblings like list_voices or list_characters. It does not explicitly distinguish itself from get_model, but the plural listing intent is unambiguous.

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?

The filtering options imply the intended use (discovering models before a generation call), but there is no explicit when-to-use or when-not-to-use statement and no pointer to get_model for single-model lookups. Usage is inferable rather than stated.

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