Skip to main content
Glama

List Models

list_models
Read-only

List the AI image, video, music, sound-effect, and 3D models available on BudgetPixel, plus the depth-map tool's sizes, with standard credit prices and capabilities. Featured models come first with a one-line role hint (when to pick each). Image models that charge by output size list every size's price (the size you pass as resolution sets the price). Video models are priced per SECOND by resolution; music models are flat per track unless noted (sonilo-music per second, eleven-music-v2.5 per minute billed per second); sound effects are per second with a 3-second minimum; 3D models are priced per job (base price plus named options); depth maps (generate_depth_map) are priced per second of the input video by model size (small / base / large), 5-second minimum. Prices shown are standard rates in credits. Video resolutions delivered as H.265 (HEVC) instead of H.264 are marked, because some browsers cannot play H.265.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses substantial behavioral context: pricing units by model type, minimum charges, per-size and per-second billing rules, featured ordering, role hints, and H.265 playback caveats. This gives an agent useful expectations about what the listing contains and how to interpret it.

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?

The description is dense but front-loaded, starting with the core listing purpose before detailing pricing rules. It is appropriately sized for the complexity of the catalog, though the long semicolon-heavy paragraph could be more scannable with structure.

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?

With no output schema and no parameters, the description carries the full burden of explaining return content, and it does so thoroughly: model categories, prices, capabilities, featured ordering, role hints, billing units, minimums, and H.265 marking. An agent has enough information to call and interpret the tool correctly.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description does not need to compensate for any schema gaps.

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?

The description opens with a specific verb and resource: it lists available AI image, video, music, sound-effect, and 3D models, plus depth-map sizes, prices, and capabilities. This clearly distinguishes a catalog-listing tool from generation siblings such as generate_image or generate_video.

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 implied by the catalog purpose, but the description does not explicitly say when to call this tool versus alternatives, nor does it state prerequisites or when not to use it. The mention of featured models having a 'when to pick each' hint describes output content, not guidance for invoking list_models itself.

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.