@jam-jam/convert-mcp

Get a stem separation status

jj_stems_get_job

Fetches the status of an audio stem-separation job by ID, including state, queue position, progress, time estimates, and available stem names when complete.

Instructions

Fetches the state of one of your separations by id (GET /stem-tool/jobs/{id}): state (uploading, queued, running, saving, done, failed, cancelled, expired), queue position, processed seconds against duration, time estimates, and, once done, the names of the stems available. A job unknown or belonging to another account answers the same 404. Costs no quota (read rate limit, 240 per minute): poll no faster than every few seconds.

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_stems_get_job"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Job id returned by jj_stems_separate (a UUID).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full load and does so well: it discloses the complete state machine (uploading through expired), the quota and rate-limit profile, and the notable error semantic that both unknown ids and other accounts' jobs return an identical 404, which prevents an agent from retrying and misinterpreting the failure.

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?

The purpose and endpoint lead the sentence, followed by return fields, error behavior, and cost guidance, all of which earn their place. The long parenthetical of state values is dense, keeping it just short of ideal.

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's field enumeration substitutes for one, and it covers cost, rate limits, error semantics, and polling etiquette for a single-parameter read tool. An agent can call and correctly interpret this tool without opening anything else.

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 100%, and the schema already states the id is a UUID returned by jj_stems_separate. The description only restates 'by id' and adds nothing about format or scoping beyond what the schema provides, 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 (fetches the state) and resource (a separation job) and pins it to the endpoint GET /stem-tool/jobs/{id}. It also enumerates what comes back (state, queue position, processed seconds, ETA, stem names), which clearly separates it from the sibling list and cancel tools without needing their schemas.

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 specifies how to use it (look up by job id) and gives concrete polling guidance ('poll no faster than every few seconds') plus the rate-limit allowance and zero quota cost. It doesn't explicitly name an alternative such as jj_stems_list_jobs for enumerating jobs, so it falls short of the 5 bar.

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