Skip to main content
Glama

List models

list_models
Read-only

Image and video models available, their native aspect ratios, video durations and typical render time.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-mutating read. The description adds useful output context and appropriately qualifies render time as "typical," but does not clarify whether availability is live, whether the list is exhaustive, or how render-time estimates should be interpreted.

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?

A single compact statement front-loads the model types and then enumerates the supplied attributes. There is no filler or redundancy, and every phrase contributes useful scope or output 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?

For a zero-argument, read-only listing tool, this provides enough information to understand the resource and invoke the tool. Because there is no output schema, it would be more complete if it confirmed whether caller-usable model identifiers are returned and clarified the scope or freshness of "available."

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the zero-parameter baseline applies and no parameter documentation is needed. The description is consistent with the empty schema and does not imply unsupported filters or options.

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 identifies an image and video model catalog and specifies its contents: native aspect ratios, video durations, and typical render time. Although phrased as a fragment, it conveys the purpose well; it does not explicitly differentiate the tool from sibling listing or generation tools.

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?

The listed metadata implies using the tool to inspect or compare models before selecting one for image or video generation. However, there is no explicit workflow context, when-to-use instruction, exclusion, or named alternative.

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.

Resources