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

@jam-jam/convert-mcp

by titouannwtt

Cancel a Mastering render

jj_mastering_cancel_job

Cancels one of your own audio mastering renders and deletes its files. Unfinished renders refund the consumed quota, so stop a render to reclaim credits.

Instructions

Cancels one of your own renders and deletes its files (DELETE /mastering/jobs/{id}). The render quota already consumed is refunded when the render was not finished. Needs the mastering:write scope. Only call it when the user asked to stop that render. An unknown id, or a render 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_mastering_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by jj_master_audio.

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 to lean on, the description carries the full burden and does so: it discloses the destructive file deletion, the quota refund condition, the required mastering:write scope, and the 404 response for unknown or foreign ids. That is exactly the pre-call context an agent needs for an irreversible 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 tight sentences: action and endpoint first, then side effects, then authorization, then the usage gate. No filler, and the most decision-relevant facts (deletion, refund, scope) are front-loaded.

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 one-parameter destructive tool with no output schema, the description covers side effects, permission requirements, error semantics, and when to invoke. Nothing an agent needs in order to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single id parameter is already documented as the job id from jj_master_audio, so baseline would be 3. The description adds meaning beyond the schema by clarifying that ids are account-scoped, since another account's render returns 404.

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

Purpose4/5

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

States a specific verb and resource: cancels one of your own renders and deletes its files, with the concrete endpoint DELETE /mastering/jobs/{id}. The 'your own renders' scoping plus the 404-for-another-account note separates it from generic job tools, though it never names a sibling explicitly.

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 when-to-use condition: 'Only call it when the user asked to stop that render,' which also functions as a when-not (don't cancel unprompted). It does not point at an alternative such as jj_mastering_get_job for status checks before canceling.

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