Skip to main content
Glama

owa_lyric_edit

Edit a song's words, chords, sections, translations, or key while the app preserves notation and rejects changes that would break it. Review parts first, then apply targeted replacements or line sets.

Instructions

Change one of the user's songs part by part. You give WORDS; the app writes the song notation and refuses a change that would break it. file: the song as attached, or its name in Documents. read first: its parts and lines. replace [{find, with, part?, in?}] changes a word or phrase where it stands, every time it is sung, chords kept -- for a spelling fix or a word changed (in "translations" for the lines under); {find "[F]", with "[Fmaj7]"} changes a chord. set-lines replaces the words of sections [{part, lines}]; a line that stays half the same keeps its chords and the line under it. add-translation puts one translation line under each sung line (exactly one per line, "" keeps that line's); both take config too, for a translation's Title and Subtitle; remove-translations and remove-chords (part, else all); set-chords gives the same words with [G] chords added or moved (a chord left out stays); add-section adds part ("Verse" takes the next number; "Note" is a note for the band, never on the screen) with lines, played after after (else at the end); remove-section; rename-section part to to; set-order ["Verse 1", "Chorus x2"]; set-config Title Subtitle Artist Copyright Key Tempo Time; transpose moves every chord to key (fromKey when the song has none). locales (language-region tags, "en-US") names its languages. Every change stays UNSAVED (a * beside the name, Ctrl+Z undoes it) for the user to Save and keeps a backup owa_undo puts back -- say so. Change only what was asked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>",
      "action": "<action>"
    },
    "name": "owa_lyric_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
keyNo
fileYes
pageNo
partNo
afterNo
linesNo
orderNo
actionYes
configNo
fromKeyNo
localesNo
sectionsNo
replacementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly meets it: it discloses that the app refuses notation-breaking changes, that edits remain UNSAVED with a '*' marker and Ctrl+Z undo, and that a backup exists for owa_undo, plus preservation rules for chords and the line beneath. Remaining gaps are what happens on an unresolvable `file` and what `read` actually returns beyond 'its parts and lines'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Given 13 actions and 14 parameters the density is defensible and the purpose is front-loaded, but the whole thing is a single unbroken run-on paragraph with heavy backtick and parenthetical nesting, making per-action reference hard. A short enumerated structure would have preserved the content while making it far easier to scan.

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 a high-complexity, unannotated, no-output-schema mutation tool, the description covers the action space, the mutation/undo lifecycle, and most parameter meanings, so an agent can invoke it correctly. The omissions that matter are the undocumented `page` parameter and the unstated return shape of the `read` action.

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 description coverage is 0% across 14 parameters, so the description must compensate, and it largely does: it defines `file`, every `action` value, the shape of `replacements` (including the `in` enum values), `sections`, `config` keys, `locales`, `key`/`fromKey`, `after`, `to`, `order`, and `lines`. The `page` parameter is never mentioned anywhere, and `part` is only explained piecemeal through the action prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource ('Change one of the user's songs part by part') and follows with the WORDS/notation contract, which tells an agent exactly what class of operation this is. It stops short of explicitly differentiating from siblings such as owa_lyric_file or owa_lyric_validate; owa_undo is mentioned only as the backup mechanism, not as an alternative for a competing need.

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

Usage Guidelines4/5

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

Each action carries its own when-to-use context ('for a spelling fix or a word changed', '`in` "translations" for the lines under', 'a chord left out stays'), and the sequencing rule '`read` first: its parts and lines' is stated explicitly. The closing instruction 'Change only what was asked' constrains scope. There is no statement of when NOT to use this tool or which sibling to prefer for validation or file creation.

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