Skip to main content
Glama

Use a cover

use_cover
Idempotent

Puts one of the song’s covers in use Everything made from now on uses it; videos already made keep theirs. A made cover's colours and typeface become the artist's look for their next covers. Refused (409 song_busy) while a video of the song is being made. No plan needed.

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": "use_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id
cover_idYesThe cover id (cover_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important side effects: future creations use the selected cover, existing videos keep theirs, and a made cover's colours and typeface become the artist's look for next covers. It also documents the 409 song_busy conflict and that no plan is needed, which is exactly the behavioral context an agent 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?

The description is compact and mostly front-loaded, stating the core action first and then the downstream effects and conflict. The first sentence is slightly run-on because a period is missing after 'in use', but there is no significant wasted wording.

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 mutation tool without an output schema, the description covers the key side effects, the conflict case, and the lack of a plan requirement. It does not describe the response or explain how the cover must already have been made, but the definition is otherwise complete enough to call correctly.

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 song_id and cover_id are already fully documented in the schema. The description implies that cover_id must identify one of the song's covers, but it adds no syntax or format details beyond the schema baseline.

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?

The description states a specific verb and resource: it puts one of the song's covers in use. It is clear what the operation does, but it does not explicitly distinguish this from the sibling set_song_cover, which may sound similar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful constraints such as 'No plan needed' and the 409 song_busy refusal while a video is being made. However, it does not explicitly say when to use this tool versus alternatives like set_song_cover or make_cover, so the usage guidance is only implied.

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