Skip to main content
Glama

Delete a cover

delete_cover
DestructiveIdempotent

Deletes one of the song’s covers for good Its files go too. Deleting the cover in use leaves the song without one (409 song_busy while a video of the song is being made). Ask the user first.

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": {
      "song_id": "<song_id>",
      "cover_id": "<cover_id>"
    },
    "name": "delete_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id
cover_idYesThe cover id (cover_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing that the underlying files are permanently removed, that deleting the cover in use leaves the song without a cover, and that a 409 song_busy occurs while a video is being rendered. The explicit 'ask the user first' confirmation requirement is exactly the kind of behavioral context a destructive tool needs.

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?

Short and front-loaded, with the permanence warning first and the confirmation instruction last. Minor flaw: 'for good Its files go too' is missing punctuation, which slightly hampers parsing.

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 destructive two-parameter tool with no output schema, the description covers data loss, state consequences, and the expected error case. It omits what happens if the cover or song does not exist, but nothing essential to correct invocation is missing.

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%, so both required parameters (song_id, cover_id) are already documented in the schema. The description only implies the song/cover relationship without adding format or constraint details, so the baseline 3 applies.

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 (delete one of the song's covers) and clarifies the in-use case, which distinguishes it from the cover-setting siblings. It does not name an alternative tool explicitly, so it stops short of a 5.

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 directive to confirm with the user before calling and explains the failure condition (409 song_busy while a video of the song is being made). It never routes to an alternative such as replacing the cover instead of deleting it, so guidance is clear on when to use but not on what else to use.

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