Skip to main content
Glama
@jam-jam/convert-mcp

@jam-jam/convert-mcp

by titouannwtt

Queue an audio file for chord and lyrics analysis

jj_audio_analyze

Uploads a local audio file to the Jam Jam queue to analyze its chords and lyrics and align them to an existing notebook song, returning a job to track.

Instructions

Uploads a local audio file (path, or base64 content) to the Jam Jam server queue so that its chords and lyrics are analysed, then automatically aligned, for a song of YOUR notebook (POST /audio). Same queue as the Jam Jam app. "songId" must already exist in the caller's notebook (see jj_list_songs), otherwise 404. Needs an account and the audio:write scope. It returns at once with a job: follow it with jj_queue_get_job. Idempotent per (account, song, file content): sending the same file again returns the same job with reused=true and consumes nothing. Quota: counter "audio-analysis", 5 analyses per ISO week on a free account (resets Monday 00:00 UTC), no limit on Premium; at most 50 jobs may wait per account. Errors: 413 file too large, 415 not audio, 429 quota or queue full.

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": {
      "songId": "<songId>"
    },
    "name": "jj_audio_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute or relative local path to the audio file. Mutually exclusive with contentBase64.
songIdYesId of an existing song in the caller's notebook (base song id from jj_list_songs).
filenameNoFile name (with extension). Required with contentBase64; defaults to the basename of "path".
contentBase64NoBase64-encoded audio content. Mutually exclusive with path. Requires "filename".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, and the description carries the full burden well: it discloses async behavior (returns a job immediately), idempotency keyed on account/song/content with reused=true, quota mechanics (5 per ISO week, Monday 00:00 UTC reset, Premium unlimited), a 50-waiting-job cap, required scope audio:write, and concrete error codes 413/415/429.

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?

Purpose is front-loaded, followed by prerequisites, async follow-up, idempotency, quota, and errors in a logical order with zero filler sentences. The prose is densely packed into long sentences, which slightly hurts scanability.

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?

Complete for an async, quota-limited upload tool with no output schema: it explains what is returned (a job), how to track it, what happens on repeat uploads, quota limits, and failure modes. Nothing an agent needs in order to call it correctly is missing.

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 all four parameters are already documented. The description reinforces the songId existence constraint but adds little syntax or format detail beyond the schema, so the baseline 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 (upload a local audio file to the Jam Jam queue for chord+lyrics analysis and alignment) and scopes it to a song in the caller's notebook. An agent can distinguish this from generic analysis or queue siblings without opening the schema.

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?

Gives explicit prerequisites (songId must already exist, see jj_list_songs), the follow-up path (jj_queue_get_job), and the queue shared with the Jam Jam app. It does not explicitly contrast with sibling jj_ai_music_analyze, so alternative selection is left partly to inference.

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