Skip to main content
Glama

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

list_media_models
Read-onlyIdempotent

Every media model on UplinkSwitch 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.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses that no API key is required, that data is live rather than cached ('Live from GET /v1/catalog/media'), and what each record contains, including the per-setting price breakdown and the developer's price 'where recorded' — the latter honestly flagging that the field may be absent.

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?

Three short sentences, front-loaded with what is returned and the unit semantics, followed by access and provenance details. Dense but every clause carries information; no filler.

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 returned fields and the unit basis for pricing, which is exactly what an agent needs to interpret results. The absence of explicit sibling routing is the main remaining gap for a simple two-optional-parameter list tool.

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 description coverage is 100%, so both parameters (kind, search) are already fully documented in the schema, and the description adds no filtering semantics, examples, or edge cases. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb and resource ('Every media model on UplinkSwitch') and enumerates what each entry carries (id, kind, endpoint, unit, price per setting, developer price). It does not explicitly distinguish itself from the sibling 'list_models' or 'media_model', so it falls short of the 5 bar for sibling differentiation.

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: browsing the media catalog and prices prior to generating or quoting. 'No key needed' signals accessibility, but there is no explicit when-to-use statement and no routing to alternatives like media_model (single-model detail) or media_quote (pricing estimate).

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.