Skip to main content
Glama

Archive an artist

archive_artist
DestructiveIdempotent

Remove an artist that has no songs Refused (409) while the artist still has songs.

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": {
      "artist_id": "<artist_id>"
    },
    "name": "archive_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYesThe artist id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 safety profile is covered; the description adds the useful behavior that the server returns 409 Refused when songs still exist. It does not say whether archived artists/associated photos and kit pieces are retained or restorable.

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?

It is short and front-loads the action, but the sentence is grammatically tangled ("has no songs Refused (409) while the artist still has songs"), forcing the reader to reconstruct the precondition and the error condition from fragments.

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 destructive tool with annotations covering idempotency and destructiveness, the description supplies the missing pieces: the song-count precondition and the 409 outcome. Only the post-archive state of the artist and related assets is left unexplained.

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?

Single parameter with 100% schema description coverage, so the schema carries the burden and baseline 3 applies. The description adds nothing about artist_id format or where to obtain it (e.g., from list_artists).

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 ("Remove an artist") and scopes it to artists that have no songs, which separates it from create_artist/rename_artist/get_artist. It doesn't distinguish itself from any delete-style sibling, and "Remove" reads slightly at odds with the archive_artist name, but the operation is recognizable.

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?

Explicitly gives the precondition for calling it — the artist must have no songs — which is the key usage gate for an agent. No alternatives are named and reversibility/restore paths are not mentioned, so it stops short of a 5.

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