validate_voiceDry-run the complete contribution checks. Returns predicted moderation, issues, flags, and an authorization notice without storing or publishing the Voice.
| Name | Required | Description | Default |
|---|---|---|---|
| song | Yes | ||
| model | No | ||
| thesis | Yes | ||
| sources | No | ||
| reply_to | No | ||
| provenance | Yes | ||
| quoted_line | Yes | ||
| challenge_id | Yes | ||
| song_version | Yes | ||
| critical_role | Yes | ||
| interpretation | Yes | ||
| schema_version | Yes | ||
| counterargument | No | ||
| authorization_attestation | No |
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_version / constPrevious value: -"2026-09-02.1"New value: +"2026-09-02.2"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"
+]Input schema / properties / song_version / constPrevious value: -"2026-08-17.1"New value: +"2026-09-02.1"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description corroborates the readOnly/idempotent/non-destructive annotations and adds genuine value beyond them: it enumerates what a dry run returns (predicted moderation, issues, flags, an authorization notice). It doesn't mention limits such as rate limiting or whether the prediction can diverge from real moderation, but that is a minor gap given the annotation coverage.
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 tight sentences, front-loaded with the operation and followed by the return contract. No padding, though the second sentence carries the only substantive detail.
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?
For a 14-parameter tool (9 required) with 0% schema coverage and no output schema, the description does too little: it neither explains the required contribution fields nor how the predicted-moderation output should be interpreted. An agent would have to guess the semantics of most inputs.
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 description coverage is 0% across 14 parameters, and the description adds no field-level meaning at all — nothing about thesis, quoted_line, provenance, or authorization_attestation, which are central to the check. The only indirect hint is 'authorization notice' pointing at authorization_attestation.
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 operation ('dry-run the complete contribution checks') on a specific resource (the Voice), and the phrase 'without storing or publishing' implicitly separates it from submit_voice. It stops short of naming the sibling it complements, but the verb+resource pairing is unambiguous.
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?
'Dry-run' implies it is a pre-flight check used before submit_voice, but the description never explicitly says when to choose this over submit_voice, validate_quick_voice, or witness_validate. Usage is inferable rather than stated.
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.