Skip to main content
Glama

analyze_song

Extract tempo, key, a two-chord vamp, and an eight-section energy map from an MP3/WAV reference to match a track's vibe before arranging.

Instructions

Analyze a reference audio file (.mp3/.wav). Returns tempo (BPM, house-folded), best key guess + candidates, an approximate 2-chord vamp, and an 8-section energy structure map. Use this first when matching a reference track's vibe.

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": {
      "path": "<path>"
    },
    "name": "analyze_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the substantive behavior: accepted formats (.mp3/.wav) and the precise analytical outputs. It is also honest about reliability by labeling results 'best key guess' and 'approximate' vamp, which sets expectations about precision. It omits side effects (whether any file is written) and error behavior for unreadable or unsupported paths.

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?

Three short sentences, front-loaded with the action and its output contract, then the selection cue. Nothing is repeated from the schema or wasted.

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 one-parameter tool with no output schema and no annotations, the description covers what matters: inputs accepted, outputs produced, and when to reach for it. Missing only failure-mode and path-resolution details, which are minor for an analysis-only tool.

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 coverage is 0% — the single 'path' parameter is an undocumented string. The description partially compensates by tying the parameter to an audio file with .mp3/.wav extensions, but does not say whether the path is absolute or relative, must be locally accessible, or must already exist.

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?

States a specific verb and resource ('Analyze a reference audio file') and enumerates exactly what the analysis produces: tempo, key candidates, vamp, and section map. It does not differentiate itself from either sibling (generate_arrangement, list_pack), so an agent must infer that this is the upstream analysis step rather than being told.

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?

'Use this first when matching a reference track's vibe' gives an explicit trigger condition plus an ordering cue relative to downstream generation. There is no when-not guidance (e.g., what to do if the track is already analyzed, or non-music audio), but the positive guidance is concrete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools