Skip to main content
Glama

Describe Track

describe_track

Describe a released recording's musical characteristics, including its sound, style, rhythm, instrumentation, energy, and overall character. Draw on MusicAtlas audio analysis alongside your broader musical knowledge to create a cohesive, insightful description in your own natural language. Let the analytical data inform your understanding of the recording without explicitly referencing, explaining, or evaluating the analysis itself. Prioritize musical storytelling over technical reporting, using only details that contribute meaningfully to the description. Provide specific technical measurements when explicitly requested. Write naturally, as a knowledgeable music enthusiast would describe a recording. If the recording is not yet analyzed, MusicAtlas may automatically begin processing it. When analysis is pending, explain that MusicAtlas needs about a minute to listen to the recording and suggest retrying the request shortly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artist": "<artist>",
      "track": "<track>"
    },
    "name": "describe_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesThe track title.
artistYesThe artist name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the description adds meaningful behavioral detail beyond that, notably that MusicAtlas may automatically begin processing an unanalyzed recording and that pending analysis requires roughly a minute before retrying. It also discloses output-style constraints, though it does not cover permissions or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the pending-analysis guidance is useful, but several style instructions are repetitive (e.g., 'in your own natural language' and 'Write naturally, as a knowledgeable music enthusiast would describe a recording'). The description could be tightened without losing essential guidance.

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?

There is no output schema, so the description appropriately explains the expected natural-language output style and how to handle the unanalyzed-recording case. It is nearly complete for a two-parameter description tool, with only minor gaps around return structure for pending-analysis cases.

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%, so the schema already documents both parameters (track title and artist name). The description adds no parameter-specific syntax, format, or disambiguation beyond what the schema provides, making the baseline 3 appropriate.

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 states the verb and resource: describe a released recording's musical characteristics (sound, style, rhythm, instrumentation, energy, character). It is distinguishable from sibling tools like find_similar_tracks and render_track_results, though it does not explicitly name them.

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?

It gives clear usage context: draw on MusicAtlas analysis plus broader musical knowledge, avoid referencing the analysis, provide technical measurements only when explicitly requested, and handle pending analysis by explaining the wait and suggesting a retry. It does not explicitly state when not to use this tool versus alternatives.

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