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

@jam-jam/convert-mcp

by titouannwtt

Cancel an AI music analysis

jj_ai_music_cancel_job

Cancels your AI music analysis job, deletes its temporary files, and refunds the used quota unit.

Instructions

Cancels the caller's own AI music analysis and deletes its temporary files (DELETE /ai-music/jobs/{id}). The quota unit is refunded. Needs the audio:write scope. Only call it when the user asked to stop that analysis.

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

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by jj_ai_music_analyze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses the ownership restriction, that temporary files are deleted, that the quota unit is refunded, and that the audio:write scope is required. It does not say whether cancelling is irreversible once processing is underway or what happens if the job already finished, which are the remaining behavioral gaps for an unannotated mutation tool.

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?

Three short sentences, front-loaded with the action and endpoint, then the effects, then the invocation condition. No filler and nothing repeated from the title.

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 one-parameter, no-output-schema, no-annotation cancellation tool, this covers the essentials an agent needs: identity scope, auth requirement, side effects, and the quota consequence. Only the post-cancel state semantics (irreversibility, behavior on already-completed jobs) are left implicit.

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 itself explains that id comes from jj_ai_music_analyze, so the baseline is 3. The description's "the caller's own" phrasing adds a mild constraint that the id must reference a job owned by the caller, but it adds no format or validation detail beyond the schema.

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 pairs a specific verb ("Cancels") with a specific resource ("the caller's own AI music analysis") and even names the endpoint and side effect (deleting temporary files). It also scopes ownership to the caller, which separates it from generic job tools like jj_get_job or jj_stems_cancel_job 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 gives an explicit trigger plus an exclusion: "Only call it when the user asked to stop that analysis." That is real when-to-use guidance, though it stops short of naming a concrete alternative (e.g. polling with jj_ai_music_get_job instead of cancelling).

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