Skip to main content
Glama

Rewrite a song’s brief from the song

rewrite_song_brief
Destructive

Drop the user’s correction and read the song again Writes the brief again from the song as it is now (its lyrics and analysis), in the background: the answer has status writing; poll get_song until brief.status is ready, usually within half a minute. The user’s correction (brief.edited) is dropped, so ask first. Free; a few times a day per song (429 past that). 409 while the song is being analysed.

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>"
    },
    "name": "rewrite_song_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the background/async execution model (status writing), the ~30 second expectation, the destructive consequence of dropping brief.edited, the cost (free), the rate limit (a few times a day per song, 429 past that), and the 409 conflict condition. These are exactly the behavioral facts an agent needs before calling a destructive, non-idempotent operation.

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?

The content is dense and useful, but the opening is malformed: 'Drop the user's correction and read the song again Writes the brief again...' runs two clauses together with no punctuation, which slows parsing of the most important sentence. The rest is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, destructive, asynchronous tool with no output schema, the description covers the return path (poll get_song, brief.status ready), timing, failure modes (409, 429), and the irreversible side effect. Nothing needed to call it correctly 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?

The sole parameter song_id is fully documented in the schema at 100% coverage, so the baseline applies. The description adds no meaning about the id itself beyond what the schema states.

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?

Names a specific verb and resource: it writes the song's brief again from the song as it is now, explicitly from its lyrics and analysis. That distinguishes it from edit_song_brief, since the user's correction (brief.edited) is dropped.

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 concrete operating guidance: poll get_song until brief.status is ready, expect 409 while the song is being analysed, and ask the user first because their correction is discarded. It does not name edit_song_brief as the alternative when the user wants to keep their edits, so the routing guidance is implied rather than explicit.

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