Skip to main content
Glama

list_models

Read-only

Free. Music engines with versions, credit prices, subscription requirements, songs per run, supported types (song / sound_effect / speech) and modes, and their parameter JSON schemas.

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.9/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses that the call is free and gives a detailed account of the returned metadata. It adds meaningful behavioral context, though it does not clarify whether results are exhaustive, paginated, or dynamically updated.

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?

Two compact fragments front-load the zero-cost behavior and then efficiently summarize the result contents without filler. The dense field list earns its place because there is no output schema to convey that 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 catalog tool, this provides enough information to invoke it correctly and sets strong expectations for its output. Explicit discovery guidance and any limits on result scope would make it more complete.

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 input parameters, so there are no argument semantics requiring explanation. The description appropriately focuses on the returned model metadata rather than inventing input guidance.

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 identifies the resource as music engines/models and specifies the metadata returned, including versions, prices, capabilities, and parameter schemas. The listing action relies partly on the tool name, and there is no explicit differentiation from siblings.

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 mention of supported types, modes, and parameter JSON schemas implies use for model discovery and preparation before generation or cost estimation. However, the description never explicitly states when to call it, when not to call it, or which sibling to use for another task.

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.