Skip to main content
Glama

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

list_media_models
Read-onlyIdempotent

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

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: no API key required, live data from GET /v1/catalog/media, and that prices are reported per unit 'at each setting' alongside the developer's price where recorded. It does not mention result size or whether the full catalog is always returned unpaginated, which matters for a 'every model' listing.

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 front-load the payload and the return fields, then close with the auth and source details. The phrase 'next to the developer's price where recorded' is slightly tangled but carries real information, and nothing is padded.

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?

For a two-optional-param read tool with no output schema, the description does the important work of describing the returned record shape (id, kind, endpoint, unit, price per image/second/generation/minute). The main residual gap is result-set size or pagination behavior when no filters are supplied.

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 both optional filters (kind enum and search substring) are already documented with examples in the schema. The description adds nothing parameter-specific, so the baseline of 3 applies.

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 names the exact resource (every media model on UncensoredLLM) and enumerates the fields returned (id, kind, endpoint, unit, price), so an agent knows precisely what it gets back. It stops short of explicitly distinguishing itself from catalog siblings like list_models or media_model, leaving the agent to infer that this one covers image/video/audio/3d rather than text.

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: the tool is clearly for browsing the media catalog and prices, and 'No key needed' signals it is a safe public discovery call. There is no explicit when-to-use versus media_model/media_quote, and no statement of when not to call it.

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.