Skip to main content
Glama

What to tidy in the Library

tidy_library
Read-onlyIdempotent

A read-only report on the artist's Library: possible duplicates (same size and type), files linked to no song, album or release, files with none of the artist's own tags, and how many no Promo post uses. Counts, with the newest files of each as examples. Changes nothing; offer update_media or delete_media from it, and ask the artist first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tidy_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
sampleNoExample files per group (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive, and the description reinforces this with "Changes nothing" and adds useful context: results are counts with newest-file examples, and remediation must be confirmed with the artist. It does not discuss cost, pagination, or performance on large libraries, but the safety and workflow profile is well covered.

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?

It is a compact, front-loaded block: what the report contains, what it returns, and what not to do. The fragment "how many no Promo post uses" is grammatically awkward and costs a moment of parsing, which keeps it from a 5.

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?

With no output schema, the description does the work of explaining that results are per-category counts with example files, which is enough for an agent to anticipate the response. The label-versus-artist-connection nuance is fully handled by the schema, so nothing critical is missing, though the absence of any output schema means a little more detail on result shape could have helped.

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 the label-only `artist` parameter and `sample` are already documented in the schema. The description only implicitly adds that examples are the newest files per group, which clarifies `sample` slightly but adds no syntax or default information beyond the schema, so the baseline 3 applies.

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?

It uses a specific verb-plus-resource ("read-only report on the artist's Library") and enumerates exactly which problem categories appear in the report: duplicates, orphaned files, files without the artist's own tags, and unused Promo posts. It also distinguishes itself from the sibling tools that fix these problems (update_media, delete_media).

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

Usage Guidelines5/5

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

It states that the tool changes nothing and explicitly directs the agent to follow up with update_media or delete_media, plus a gating instruction to "ask the artist first." This makes both the use case and the workflow order explicit, with no alternative left to guess.

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