Skip to main content
Glama

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

list_media_models
Read-onlyIdempotent

Every media model on PentestLLM 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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuinely new behavioral facts: no API key is required and the data is live from GET /v1/catalog/media. It stops short of saying whether the full listing is paginated or how large it can get, which matters for an "every model" call.

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 tight sentences, front-loaded with what is listed and what fields come back, followed by the auth and source details. The price-unit phrase ("per image, second, generation or minute at each setting") is dense but earns its place by clarifying the unit field's variability.

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 describing returns and does so field-by-field, plus auth and data source for a read-only catalog tool. The only gap is scale behavior (pagination or result size) for a listing that claims to return every model.

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%, with kind's enum and search's substring behavior fully documented in the schema. The description adds no filter semantics of its own — it never mentions kind or search — so it neither compensates for nor extends the schema; baseline 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 a specific resource (every media model on PentestLLM) and enumerates what comes back: id, kind, endpoint, unit and price per image/second/generation/minute. It is clearly a catalog-listing tool, distinguishable in spirit from media_model or media_quote, but it never names those siblings to make the distinction explicit.

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?

"Every media model" plus "No key needed" implies this is the browse-the-whole-catalog, unauthenticated entry point, which is useful context. However, there is no explicit when-to-use statement and no exclusion pointing to media_model (single-model detail) or media_quote (pricing), so the agent must infer routing from sibling names alone.

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.