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

@jam-jam/convert-mcp

by titouannwtt

Get an AI music analysis and its report

jj_ai_music_get_job

Fetches an AI music analysis job by ID to check status, queue position, and progress, and returns the completed report with signal score, verdict, and detector windows.

Instructions

Fetches one AI music analysis by id (GET /ai-music/jobs/{id}): state (uploading, queued, running, cancelling, done, failed, cancelled), progress, queue position and, once done, the report in "result" (score 0 to 100, verdict signals-detected / few-signals / inconclusive, per-detector windows, and for the v3 report the classification human / processed-ai / pure-ai). The report is an aggregated index of signals, not a probability and not proof of origin: present it as such. A job of another account answers 404. Needs the queue:read scope. Costs no quota.

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": {
      "id": "<id>"
    },
    "name": "jj_ai_music_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by jj_ai_music_analyze (a UUID).

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?

With no annotations supplied, the description carries the full burden and does so: it lists all six job states, mentions progress and queue position, describes when "result" is populated, and flags that the report is an aggregated signal index rather than a probability or proof of origin. It also discloses the 404-for-other-accounts rule, the queue:read scope requirement, and that the call consumes no quota.

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?

It is front-loaded with the core action and endpoint, and every clause carries operational information (states, report contents, auth, quota, error case). The middle is a single very long sentence that packs state enumeration and report semantics together, which is dense but not padded.

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?

There is no output schema, so the description must explain the return value, and it does: field names, the score range 0-100, the three verdict values, per-detector windows, and the v3 classification values. Combined with the id source, auth scope, quota note, and interpretation caveat, nothing an agent needs to call or report on this tool 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?

There is a single parameter with 100% schema description coverage, and the schema already states that the id is the UUID returned by jj_ai_music_analyze. The description restates that origin but adds no new constraints, format details, or edge cases about the id itself, so the baseline 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?

The description opens with a specific verb and resource ("Fetches one AI music analysis by id") and names the underlying endpoint (GET /ai-music/jobs/{id}), then enumerates exactly what comes back. An agent can tell this is a single-job status/report read, distinct from listing tools like history or current.

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 states where the required id comes from ("Job id returned by jj_ai_music_analyze"), which gives clear entry context, plus prerequisites (queue:read scope) and a failure case (another account's job returns 404). It stops short of explicit exclusions such as when to prefer jj_ai_music_current or jj_ai_music_history over an id lookup.

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