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

@jam-jam/convert-mcp

by titouannwtt

Cancel a stem separation

jj_stems_cancel_job

Stops one of your own stem separations while it is still uploading, queued or running, for cases where the user asked to cancel that job. Returns 404 for unknown or foreign job ids.

Instructions

Cancels one of your own separations that is still uploading, queued or running (DELETE /stem-tool/jobs/{id}). Needs the stems:write scope. Only call it when the user asked to stop that separation. Costs no quota. An unknown id, or a job of another account, answers 404.

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

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by jj_stems_separate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does it well: it discloses the required stems:write scope, that the call costs no quota, and the 404 behavior for unknown ids or another account's job. It leaves open whether cancellation is immediate/irreversible and what happens to partial outputs, which are meaningful gaps for a destructive-sounding operation.

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?

Four short sentences, each carrying a distinct fact (scope, endpoint, auth, trigger condition, cost, error behavior), with the core action front-loaded. No filler or repetition.

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 single-parameter mutation with no annotations and no output schema, the definition covers auth, quota impact, state preconditions and error semantics. The only missing piece is what a successful response looks like or whether partial artifacts are cleaned up, which an agent would reasonably want to know.

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 explains that id is 'Job id returned by jj_stems_separate'. The description only adds the ownership constraint ('one of your own separations') and the {id} path position, so it adds little beyond the structured field — 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 (cancels) and a precisely scoped resource (one of your own separations still uploading, queued or running), plus the underlying endpoint DELETE /stem-tool/jobs/{id}. This distinguishes it cleanly from jj_stems_get_job, jj_stems_list_jobs and jj_stems_separate without the agent needing to open another 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 a clear activation condition — 'Only call it when the user asked to stop that separation' — and an implicit exclusion via the state precondition (jobs that already finished are out of scope). It does not name a sibling to consult first (e.g. a get-job call to confirm status), so it stops short of full when/when-not/alternative guidance.

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