Skip to main content
Glama

list_models

Retrieve available image, video, and audio generation models with IDs, aspect or voice choices, options, and credit prices; filter by media kind to compare options before generating.

Instructions

List available generation models with their ids, aspect/voice choices, options and credit prices.

kind: optional filter - "image", "video" or "audio".

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
kindNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the payload contents (ids, aspect/voice choices, options, credit prices), which is genuinely useful behavioral context, but it says nothing about whether the call is read-only, whether pricing is per-call or per-credit unit, rate limits, or pagination. Adequate but with clear disclosure gaps for an unannotated tool.

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 short lines, front-loaded with what the tool returns. The second line is formatted as a pasted schema field note ("kind: optional filter..."), which is slightly awkward in a description but wastes no words.

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?

One optional parameter, flat schema, and an output schema exists so return values need no further explanation. The description covers purpose, filter values, and payload contents; the only shortfall is the unstated behavior when `kind` is null, which is minor for a tool this simple.

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 coverage is 0% and the `kind` property is a bare anyOf string/null with no enum, so the schema tells the agent nothing. The description supplies the actual accepted values ("image", "video", "audio") that the schema omits, which is real added meaning. It stops short of stating the default behavior when the filter is omitted.

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?

"List available generation models with their ids, aspect/voice choices, options and credit prices" gives a specific verb (list) and resource (models) plus the shape of the returned data. It is clearly distinct from the action siblings (generate_image, upscale_image) and from get_balance, though it never names or contrasts those alternatives explicitly.

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?

Usage is only implied: the mention of ids and credit prices suggests calling this before a generate_* call to discover model identifiers and cost. There is no explicit "use this when...", no statement about omitting the filter (all models), and no routing to any sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.