Skip to main content
Glama

Image and video models

list_generation_models
Read-onlyIdempotent

The image and video models you can use here, with the same names as the Image and Video pages, their options and credit prices, and what making a character costs. Image models pick their create or edit version automatically. Video models list what they take (start or end image, reference files, a video to extend) and whether they can say a line in your character's own voice (talkingClips).

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_generation_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description still adds real behavioral content beyond them: image models auto-select create vs edit variants, video models enumerate accepted inputs (start/end image, reference files, video to extend), and a talkingClips capability flag. It does not discuss result size, caching, or refresh cadence, but for a read-only catalog that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the second and third sentences are dense run-ons packing several distinct facts (auto create/edit selection, input types, talkingClips) into prose without structure. A short bulleted enumeration or a sentence per model family would scan faster; as written it is readable but rambling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explaining what comes back, and it does list the return fields loosely (names, options, credit prices, character costs, accepted inputs, talkingClips). However, it omits the output shape entirely (record fields, nesting) and leaves the only input parameter unexplained, which is a meaningful gap for a catalog tool an agent must filter correctly.

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

Parameters2/5

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

There is one parameter, `kind`, with an enum of image/video/character/all and a default of 'all', but schema description coverage is 0% and the description never mentions a filter at all. An agent reading only the prose would not know the result can or should be narrowed by kind, even though 'character' and 'what making a character costs' gestures vaguely at one of the values.

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?

The description states the resource (catalog of image and video models) and enumerates what the listing contains: names matching the Image/Video pages, options, credit prices, character costs. It is clear what the tool returns, though the verb itself is only implied ('the models you can use here') rather than stated as 'list'.

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 credit prices and character costs hints you should call this before spending credits or configuring a generation. There is no explicit 'use this when...' guidance, no mention of when-not to call it, and no pointer to the sibling cost-estimation tool (estimate_cost) an agent would likely pair with it.

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