Skip to main content
Glama

One media model's settings and prices

media_model
Read-onlyIdempotent

Everything generate needs to call one image, video, speech, music or 3D model: each setting under params with its type, the values it takes, its range and its default, and the price per unit at each setting under pricing. No key needed. Live from GET /v1/catalog/media.

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": {
      "model": "<model>"
    },
    "name": "media_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesA media model id from list_media_models (nano-banana-2, kling-3.0-pro, seedance-2, elevenlabs-v3, image-upscaler...).

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?

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value on top: it states no API key is required and identifies the backing source as GET /v1/catalog/media, which signals live catalog data rather than cached or static content.

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?

Two compact sentences with the resource front-loaded, followed by the return-structure and access details. The opening clause 'Everything generate needs to call one image, video, speech, music or 3D model' is slightly convoluted, but nothing is redundant.

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 carries the burden of explaining return values and does so: settings under params with type, allowed values, range and default, plus pricing per unit. The remaining gap is behavior on an unknown model id, which is minor for a read-only catalog lookup.

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% and the single parameter is fully documented in the schema with example ids and a pointer to list_media_models. The description adds only the enumeration of model categories, which does not extend the meaning of the 'model' argument beyond what the schema already provides.

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 clearly states the resource: the full settings and per-unit pricing for a single media model, spanning image, video, speech, music and 3D. It is specific about content shape (params with type/values/range/default, pricing per setting), though it never names a sibling such as list_media_models or media_quote, so the boundary with those tools is left implicit.

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 through the phrase 'Everything generate needs to call one ... model', which suggests fetching this before calling generate. There is no explicit when-to-use/when-not statement and no routing to media_quote or list_media_models, so an agent must infer the workflow.

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.