read_songSTART HERE: read complete canonical lyrics for one historical song. Try song=discipline, quote one exact line, and prepare a specific interpretation before considering any authorized publication.
| Name | Required | Description | Default |
|---|---|---|---|
| song | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / song / enumPrevious value: -[
- "austerlitz-sun",
- "blood-for-blood",
- "broken-mirrors",
- "cheers-to-fritz",
- "discipline",
- "farmington-mourning",
- "gettysburg-ballad",
- "hungry-winter-1780",
- "italy-will-be-made",
- "lancasters-ribbon",
- "leipzig-watch",
- "light-brigade",
- "montreal-smile",
- "old-ironsides",
- "open-blockhouse",
- "rum-alabama-rum",
- "send-the-italian",
- "shiloh-ballad",
- "white-shirts-borodino",
- "the-elephant",
- "tim-and-jones",
- "waterloo-smile"
-]New value: +[
+ "andersonville-prisoner",
+ "austerlitz-sun",
+ "blood-for-blood",
+ "broken-mirrors",
+ "cheers-to-fritz",
+ "discipline",
+ "fare-you-well-my-darling",
+ "farmington-mourning",
+ "gettysburg-ballad",
+ "hungry-winter-1780",
+ "i-havent-found-the-ending-yet",
+ "it-has-to-mean-something",
+ "italy-will-be-made",
+ "lancasters-ribbon",
+ "leipzig-watch",
+ "light-brigade",
+ "montreal-smile",
+ "old-ironsides",
+ "open-blockhouse",
+ "rum-alabama-rum",
+ "send-the-italian",
+ "shiloh-ballad",
+ "some-dreams-only-sleep",
+ "the-elephant",
+ "the-nation-born-at-appomattox",
+ "tim-and-jones",
+ "waterloo-smile",
+ "white-shirts-borodino"
+]Input schema / properties / song / enumPrevious value: -[
- "austerlitz-sun",
- "blood-for-blood",
- "broken-mirrors",
- "cheers-to-fritz",
- "discipline",
- "farmington-mourning",
- "gettysburg-ballad",
- "hungry-winter-1780",
- "italy-will-be-made",
- "lancasters-ribbon",
- "leipzig-watch",
- "light-brigade",
- "montreal-smile",
- "old-ironsides",
- "open-blockhouse",
- "rum-alabama-rum",
- "send-the-italian",
- "shiloh-ballad",
- "the-elephant",
- "tim-and-jones",
- "waterloo-smile"
-]New value: +[
+ "austerlitz-sun",
+ "blood-for-blood",
+ "broken-mirrors",
+ "cheers-to-fritz",
+ "discipline",
+ "farmington-mourning",
+ "gettysburg-ballad",
+ "hungry-winter-1780",
+ "italy-will-be-made",
+ "lancasters-ribbon",
+ "leipzig-watch",
+ "light-brigade",
+ "montreal-smile",
+ "old-ironsides",
+ "open-blockhouse",
+ "rum-alabama-rum",
+ "send-the-italian",
+ "shiloh-ballad",
+ "white-shirts-borodino",
+ "the-elephant",
+ "tim-and-jones",
+ "waterloo-smile"
+]Input schema / properties / song / enumPrevious value: -[
- "austerlitz-sun",
- "blood-for-blood",
- "broken-mirrors",
- "cheers-to-fritz",
- "discipline",
- "farmington-mourning",
- "gettysburg-ballad",
- "hungry-winter-1780",
- "italy-will-be-made",
- "lancasters-ribbon",
- "leipzig-watch",
- "light-brigade",
- "montreal-smile",
- "old-ironsides",
- "rum-alabama-rum",
- "send-the-italian",
- "shiloh-ballad",
- "the-elephant",
- "tim-and-jones",
- "waterloo-smile"
-]New value: +[
+ "austerlitz-sun",
+ "blood-for-blood",
+ "broken-mirrors",
+ "cheers-to-fritz",
+ "discipline",
+ "farmington-mourning",
+ "gettysburg-ballad",
+ "hungry-winter-1780",
+ "italy-will-be-made",
+ "lancasters-ribbon",
+ "leipzig-watch",
+ "light-brigade",
+ "montreal-smile",
+ "old-ironsides",
+ "open-blockhouse",
+ "rum-alabama-rum",
+ "send-the-italian",
+ "shiloh-ballad",
+ "the-elephant",
+ "tim-and-jones",
+ "waterloo-smile"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that output is 'complete canonical lyrics' rather than excerpts, which is useful, but says nothing about length, formatting, or whether multiple songs can be fetched.
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 'START HERE' so the entry-point role is immediately visible. The 'quote one exact line, and prepare a specific interpretation' clause is workflow flavor that slightly pads an otherwise tight definition.
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?
There is no output schema, so the description usefully states that complete lyrics are returned. With annotations covering safety and a single enum-constrained parameter, an agent has enough to invoke it correctly; only the relationship to search_corpus/campfire_catalog is left implicit.
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?
Schema coverage is 0%, so the description must carry the parameter burden. It clarifies that 'song' is a historical-song identifier and supplies a concrete example (song=discipline), which helps despite the enum already listing valid values; it does not explain naming conventions or what happens with an invalid slug.
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?
States a specific verb and resource: 'read complete canonical lyrics for one historical song.' That clearly separates it from search_corpus or witness_* tools, though no sibling is named explicitly, so it stops short of full differentiation.
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?
'START HERE' plus the instruction to prepare an interpretation 'before considering any authorized publication' gives real sequencing guidance relative to publication tools like submit_voice. It does not say when to prefer search_corpus or campfire_catalog instead, so it lacks explicit alternatives.
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.