Skip to main content
Glama

List Playground generation models

playground_models_list
Read-onlyIdempotent

Discover enabled image and/or video models with aspect ratios, durations, reference requirements, whether the agent can run them, and price: baseCredits (one image, or the cheapest supported video duration) and creditsByDuration for videos. Prices are list prices for planning; get the exact charge with quote: true on playground_media_generate or playground_node_run (or the *_quote tools). kind filters to image or video models; omit it for both. Discovery is optional: quote a known/requested model directly instead of listing the catalog before every generation. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "playground_models_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoModel family to list: image or video; omit to list both. image, video, or all (default).all
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
imageYes
videoYes
pricingYes
promptGuidesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only.' adds nothing; however, the description contributes real behavioral context by stating that returned prices are list prices for planning only and that exact charges require quote: true on a downstream tool. That pricing-semantics caveat is exactly the kind of information annotations cannot carry. Minor redundancy keeps it from 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.

Conciseness4/5

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

Content is front-loaded into a single dense sentence that names the resource and its returned fields, followed by pricing and usage caveats in priority order. It is somewhat packed and repeats the annotation-level 'Read-only.' fact, but no sentence is filler.

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?

For a two-parameter read-only listing tool with a full output schema and full annotation coverage, the description covers purpose, filtering, pricing interpretation, and the optionality of the call. Nothing an agent needs in order to decide whether and how to invoke it 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%, so baseline is 3; both kind and projectId are fully described in the schema, including the enum and default. The description's 'kind filters to image or video models; omit it for both' largely restates the schema, and projectId is not addressed at all, so no meaningful meaning is added beyond structured data.

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 ('Discover') and resource ('enabled image and/or video models') and enumerates exactly what comes back: aspect ratios, durations, reference requirements, runnability, and price. An agent can distinguish this catalog-listing tool from playground_media_generate or playground_node_run without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-not guidance ('Discovery is optional: quote a known/requested model directly instead of listing the catalog before every generation') and directs the agent to the precise alternative mechanism (quote: true on playground_media_generate / playground_node_run). It also explains the kind filter's default behavior, removing the main selection ambiguity.

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.