Skip to main content
Glama

Let a song import go

cancel_song_import
DestructiveIdempotent

Remove a failed (or queued) import from the list Its song isn’t made; it can be imported again later.

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": {
      "import_id": "<import_id>"
    },
    "name": "cancel_song_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_idYesThe import id (import_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description adds real value by scoping the destruction: only the list entry goes away, the song is not created, and the import can be retried later. It does not say what response is returned or whether partially uploaded assets are cleaned up.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, but the first is a run-on missing its period ('from the list Its song isn't made'), which momentarily garbles the sentence boundary. The retry reassurance is front-loaded appropriately.

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 mutation with no output schema and full annotation coverage, the description supplies the essential outcome (nothing is produced, retry is possible). Only the follow-up state — whether the import id becomes invalid or partially uploaded audio remains — is left open.

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 description coverage is 100% for the single import_id parameter, so the schema already carries the format hint ('import_…'). The description adds no further meaning about the identifier, which is the expected baseline at high coverage.

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?

Specific verb plus resource: 'Remove a failed (or queued) import from the list,' with the qualifying states named. It clearly separates this from reading an import (get_song_import) or listing imports, 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?

The parenthetical 'failed (or queued)' effectively states the condition under which the tool applies, implying it should not be used on already-completed imports. No explicit exclusion or named alternative is given, so it falls short of a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources