Skip to main content
Glama

list_song_tools

Read-only

Free. Prices, requirements and limits of every re-creation, processing, voice cover and upload tool. Call before quoting a price for these tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already declares this is a safe read, but the description adds context annotations cannot: the call is free (no credits consumed) and the payload is pricing/requirements/limits metadata. It does not describe result shape or pagination, but for a zero-parameter catalog call the disclosure is adequate.

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 short sentences with the cost fact front-loaded and the usage trigger second; nothing is wasted. The opening 'Free.' as a fragment is slightly abrupt, and the middle sentence is a heavy noun stack, but neither costs the reader much.

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 simple, parameterless, read-only catalog tool with no output schema, the description tells the agent what it returns and why to call it. The main gap is the unstated boundary with estimate_credits, which an agent doing cost work may need to resolve.

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 takes no parameters, so the baseline of 4 applies. The description correctly implies the catalog is unfiltered, covering 'every' supported tool rather than a subset.

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 concrete resource set (prices, requirements and limits of re-creation, processing, voice cover and upload tools), so an agent can tell this is a static pricing/requirements catalog rather than a generation call. It is clear but slightly indirect about the verb, relying on 'list' from the name and a dense noun phrase to convey what is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call before quoting a price for these tools' gives an explicit, actionable trigger for invocation. It stops short of naming or excluding alternatives such as estimate_credits, so an agent is not told when a computed credit estimate is preferable to reading this catalog.

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.