Skip to main content
Glama

List image, video, speech and 3D models and prices

list_media_models
Read-onlyIdempotent

Every media model on RelaySwitch with its id, kind, endpoint, unit and price per image, second, generation or minute at each setting, next to the developer's price where recorded. No key needed. Live from GET /v1/catalog/media.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly models of this kind.
searchNoA substring of the model id or name (nano-banana, veo, kling...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond them: no authentication key is required, and results come 'live from GET /v1/catalog/media' rather than a cached snapshot, which tells the agent prices are current.

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 sentences, front-loaded with the resource and its returned fields, followed by the key-free and live-source facts. No filler or repetition; every clause carries information.

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?

With no output schema, the description compensates by enumerating the returned fields, including per-unit pricing across settings and an optional comparison developer price. Combined with the two optional filters and the auth note, an agent has enough to call it correctly; only the distinction from the single-model sibling is unstated.

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 both parameters carry descriptions plus an enum for kind, so the schema does the heavy lifting. The description adds no filtering semantics beyond what the schema provides — 'at each setting' refers to returned pricing tiers, not to an input parameter.

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 a specific resource (every media model on RelaySwitch) and enumerates what comes back — id, kind, endpoint, unit, and per-setting price — so an agent knows exactly what a call yields. It does not name a sibling such as media_model or list_models to distinguish single-model lookup from catalog listing, which keeps it below a 5.

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 framing, and 'No key needed' signals it is safe to call early without credentials. There is no explicit when-to-use versus media_model (detail) or media_quote (pricing for a specific run), and no stated exclusions, so guidance is adequate but inferential.

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.