Skip to main content
Glama

Models and prices

list_models
Read-only

Lists the genframe models available to this account with their price in credits per option, aspect ratios, resolutions, durations and which inputs (reference pictures, first/last frame) they take. Call it before generating if you are unsure which model or option to use. Free.

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
kindNoOnly picture models, only video models, or all (default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavioral information by stating 'Free', which tells the agent this discovery call consumes no credits and is safe to call speculatively. It does not discuss response size or ordering, keeping it below 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.

Conciseness5/5

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

Two short sentences: the first front-loads the substantive payload enumerating returned fields, the second gives the call trigger and cost. No filler and no repetition of the name.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must characterize the response — and it does, listing price, options, aspect ratios, resolutions, durations, and accepted inputs. For a zero-required-parameter, single-enum listing tool, nothing an agent needs is missing.

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 coverage is 100% and the single 'kind' parameter already carries an enum plus a description of its three values, so the schema does the work. The description adds no filtering syntax or default behavior beyond that, which is the baseline-3 case for a fully documented 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?

States a specific verb and resource ('Lists the genframe models available to this account') and enumerates exactly what each entry contains (price in credits, aspect ratios, resolutions, durations, accepted inputs). That detail separates it cleanly from siblings like list_presets, list_generations, and the generate_* tools.

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?

'Call it before generating if you are unsure which model or option to use' gives a concrete trigger condition tied to the generate_* siblings. It stops short of a negative case (e.g. skip it when you already know the model ID), but the intended placement in the workflow is unambiguous.

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