list_releasesUse this when an agent needs to list public album and release records. Do not infer ownership, licensing, or unpublished availability.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint and non-destructive behavior, so the bar is lower. The description adds valuable context by emphasizing that only public records are listed and warning against inferring ownership, licensing, or unpublished availability – information not captured in the annotations or schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the usage directive, and every word earns its place. The negative guidance ('Do not infer...') is a necessary clarification that prevents misuse without bloating the text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and an output schema present, the description covers all necessary invocation context. The positive and negative scope ('public', 'do not infer ownership...') fully defines what the tool will and will not provide.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema provides 100% coverage, so there are no parameter semantics to clarify. The description correctly focuses on behavior rather than params, which is appropriate for a parameter-less tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('list') and resource ('public album and release records'), clearly distinguishing the tool from siblings like get_release or search_music. It also sets a clear boundary on what is returned ('public' only), leaving no ambiguity about the tool's scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool ('Use this when an agent needs to list public album and release records'). It does not name alternative tools or provide 'when not to use' guidance, but the condition is clear enough for an agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: the four cyclic-scale tools cleanly separate generation, analysis, MusicXML export, and frequency calculation, while the catalog tools distinguish search, list, composition, release, track, and sheet-music lookup. There are no overlapping responsibilities that would cause an agent to misselect.
All tool names follow a consistent lowercase verb_noun snake_case pattern with clear verbs such as analyze, calculate, export, generate, get, list, and search. The singular/plural usage is logical and predictable throughout the toolset.
Ten tools is well within the ideal range and appropriately covers two cohesive subdomains: public music catalog access and cyclic-scale utilities. Each tool has a distinct purpose, and none feel redundant or merely decorative.
The catalog surface covers search, listing releases, and fetching compositions, releases, tracks, and sheet-music resources, while the cyclic-scale tools form a coherent generate-analyze-export workflow. Minor gaps exist, such as no explicit way to list tracks for a specific release or browse compositions independently of search, but agents can work around these with the existing tools.