Skip to main content
Glama

owa_lyric_validate

Validate Open Lyric notation and get each mistake with its line, section, and correction plus song structure. Draft notation from raw text or a song URL, or find a song by title.

Instructions

Check song text in Open Lyric notation -- the Lyric Editor's format: every mistake with its line, its section and what to write instead, then what the song IS (title, key, tempo, sections, play order). For a pasted song, or one the Lyric Editor marks red or will not accept. mode: "draft" writes the notation FROM raw words -- a paste, an attached file; use it, and never write the notation yourself. For a song on a web page pass its url and no text: the page is read here, whole, with every chord written in where it lands (a copy you type has none), and the answer says which part of the page it used. A song by NAME only: mode: "find" + title -- looked up in their songs and the app’s public-domain hymns.

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": "owa_lyric_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNodraft: its last words
urlNodraft: the https address of a song page.
fromNodraft: the song’s first words on the page, only if the area it reported was wrong
modeNoLeft out, notation (```ol: fences) is checked and anything else is drafted.
textNoThe song: a whole Open Lyric file to check, or the raw words to draft from. Leave out with `url`.
titleNodraft, find: its title
artistNodraft: who it is by
copyrightNodraft: whose the song is, ONLY as the page or the user wrote it -- "Public Domain", or the © line. Never from memory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and discharges most of it: it discloses the shape of check results, the metadata summary, that a page URL is read whole with chords resolved in place, and that the response reports which part of the page was used. The remaining gap is side effects — it never states whether check or draft merely returns text or actually modifies the Lyric Editor, so an agent cannot tell whether the call is a read or a write.

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?

Content is front-loaded: check behavior first, then draft, then URL, then find, matching the likely order of invocation. Sentences are long and em-dash-heavy, and the parentheticals ('a copy you type has none') add bulk, but no sentence is purely redundant.

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?

For an 8-parameter, fully-optional tool with no output schema and no annotations, the description covers what the agent needs: mode routing, input-shape preconditions, and the substance of the return value for both check and find. The one material omission is mutation semantics — whether these calls change editor state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining what `mode` selects behaviorally, by establishing the `url`/`text` mutual exclusion ('pass its `url` and no `text`'), and by tying `title` to the find and draft paths. It still leaves `from`/`to`, `artist`, and `copyright` to the schema text alone.

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?

The description opens with a specific verb and resource: 'Check song text in Open Lyric notation -- the Lyric Editor's format.' It then enumerates exactly what comes back (every mistake with line, section, suggested fix, plus title, key, tempo, sections, play order), which makes it unmistakably distinct from the sibling tools owa_lyric_edit and owa_lyric_file.

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 gives explicit triggers ('For a pasted song, or one the Lyric Editor marks red or will not accept'), plus a directive to always use draft mode rather than writing notation by hand. It also routes three input shapes to three modes: raw words to `draft`, a web page to `url` with no `text`, and a name-only lookup to `mode: "find"` + `title`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.