Skip to main content
Glama

Get karaoke lyrics

get_karaoke_lyrics
Read-only

Read a bounded range of this project's saved lyric lines and their revision, without changing processing. Use for a user-requested lyric check or correction; do not invent missing text or silently rewrite repeats. Respect content rights when discussing lyrics in chat. No review card is opened.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_karaoke_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_countNo
project_idYes
start_lineNo

Output Schema

NameRequiredDescriptionDefault
errorNo
lyricsNo
has_moreNo
line_countNo
project_idNo
start_lineNo
total_linesNo
lyrics_sourceNo
project_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, destructiveHint=false), the description adds real behavioral context: processing is not changed, no review card is opened, and content-rights handling applies when discussing lyrics in chat. The 'No review card is opened' detail is UI-level behavior an agent could not derive from the annotations. It does not explain the apparent non-idempotent hint or pagination beyond 'bounded range,' which keeps it from a 5.

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?

Three tight sentences: scope first, then usage, then constraints and UI behavior. Every clause carries information, though the content-rights sentence is policy boilerplate that is only loosely tied to invoking the tool.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description supplies scope, usage, and the no-review-card behavior, leaving only parameter conventions (indexing, defaults) unaddressed. That is a small but real gap for a 3-parameter tool.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it only partially does: 'this project's' maps to project_id and 'bounded range' hints at start_line plus line_count. It says nothing about 1-based indexing, defaults (start=1, count=50), or the 200-line cap beyond what the schema encodes numerically. The compensation is minimal, so baseline 3 is fair.

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?

States a specific verb and resource: 'Read a bounded range of this project's saved lyric lines and their revision, without changing processing.' That is far more precise than the title alone and signals a read-only scope. It does not explicitly distinguish itself from siblings like get_karaoke or replace_karaoke_lyrics by name, so it stops short of a 5.

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?

'Use for a user-requested lyric check or correction' gives a clear triggering context, and 'do not invent missing text or silently rewrite repeats' sets a boundary on behavior. There is no explicit when-not or named alternative tool, but the read-vs-rewrite split is implied strongly enough for correct selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources