Skip to main content
Glama

Read a music track

analyze_music
Destructive

Reads a track's tempo, beats, bars, drop and ending into FIT.md, cues.json and seams.png, so you can pick hit and drop points before fitting the track.

Instructions

Use it when the user wants a track's tempo, beats, bars, drop or ending. Reads a music track's tempo, beats, bars, drop and ending, and writes FIT.md (the tempo, the drop and the other drop candidates, where sections start, how it ends and any warning), cues.json (beats and bars in seconds, and as frames at 30 a second) and seams.png (the track with its bars). It changes no track, and saves in a folder of its own, apart from fit_music's for the same track. Its tempo tells which launch film look the track suits. Use it before fit_music to pick hit and drop. To fit the track, use fit_music instead. The music playbook (makersmcp_playbook) has the whole job. (musicfit 0.2.2, on this machine.)

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": {
      "track": "<track>"
    },
    "name": "analyze_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmNoThe tempo, when the one found is half or double the real one; FIT.md warns when it could be (default: found).
meterNoBeats to a bar, "3" or "4", when FIT.md warns the bars may have the other (default: found).
trackYesThe music file, or a video whose sound to read.
out_dirNoFolder to save into, absolute or relative to /app. Default: musicfit-<track-name>.analysis, where <track-name> is the name of track without its extension. A run replaces the files an earlier run of this kit left there, so give each version its own out_dir.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bpm / description
      Previous value: -"The tempo, when the one found is half or double the real one."New value: +"The tempo, when the one found is half or double the real one; FIT.md warns when it could be (default: found)."
    • addedInput schema / properties / meter / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "3",
      +      "4"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "enum": [
      +      3,
      +      4
      +    ],
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / meter / description
      Previous value: -"Beats to a bar (default: found)."New value: +"Beats to a bar, \"3\" or \"4\", when FIT.md warns the bars may have the other (default: found)."
    • removedInput schema / properties / meter / enum
      Removed value: -[
      -  "3",
      -  "4"
      -]
    • removedInput schema / properties / meter / type
      Removed value: -"string"
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: musicfit-{stem:track}."New value: +"Folder to save into, absolute or relative to /app. Default: musicfit-<track-name>.analysis, where <track-name> is the name of track without its extension. A run replaces the files an earlier run of this kit left there, so give each version its own out_dir."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations mark this as non-read-only and destructive, and the description adds real context beyond them: it writes three named files with described contents, leaves the source track unmodified, and stores output in a folder separate from fit_music's. It stops short of saying a re-run overwrites earlier files in out_dir (that caveat lives only in the schema) and says nothing about runtime duration or job_id handling.

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?

Front-loads the usage trigger and keeps the alternative and playbook pointer at the end, which is good ordering. However, the list 'tempo, beats, bars, drop or ending' is repeated almost verbatim in the first two sentences, and the trailing version stamp ('(musicfit 0.2.2, on this machine.)') is low-value for tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter analysis tool with an output schema and full annotation coverage, the description supplies everything needed to select and call it: trigger conditions, outputs, non-mutation of the source, folder isolation, sibling alternatives, and a playbook reference.

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% and the parameter docs already explain the bpm/meter overrides, the out_dir default and overwrite warning, and the wait_seconds rationale. The description adds essentially no parameter-level meaning beyond restating which measurements are produced, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Reads a music track's tempo, beats, bars, drop and ending') and enumerates the concrete artifacts written (FIT.md, cues.json, seams.png). It explicitly distinguishes itself from fit_music, so an agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it when the user wants a track's tempo, beats, bars, drop or ending'), an ordering rule ('Use it before fit_music to pick hit and drop'), an exclusion with the named alternative ('To fit the track, use fit_music instead'), and points to makersmcp_playbook for the full workflow.

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