Skip to main content
Glama

get_timed_lyrics

Read-only

Free. Line-by-line lyrics with start/end times in seconds for a completed song (for subtitles, karaoke, LRC files). status "pending" = timing is still being computed, call again in ~15s; "unavailable" = no timing for this song (instrumentals, some engines), use songs[].lyrics instead.

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": {
      "id": "<id>"
    },
    "name": "get_timed_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSong id (songs[].id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavioral facts: the call is free, timing may be asynchronously computed, and the status field can return pending or unavailable with defined follow-ups. It does not document the exact response shape for the ready case, 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?

Front-loaded with the capability, then the cost note, then the two status branches — every clause carries information. It is dense to the point of reading as one long run-on block with embedded quoted statuses, which slightly hurts scanability.

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 one-parameter read tool with no output schema, it covers cost, async status handling, and the fallback path. Only the shape of a successful payload (units are stated, but not fields like line text or ordering) is left implicit.

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 coverage is 100% and the single id parameter is already documented as songs[].id. The description adds only the implicit constraint that the song must be completed, so the schema continues to do the heavy lifting.

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?

States a specific verb+resource (line-by-line lyrics) with precise output semantics: start/end times in seconds, for a completed song, with use cases (subtitles, karaoke, LRC). It also distinguishes itself from songs[].lyrics, so an agent can tell which lyrics source to pick.

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?

Gives explicit conditional guidance: pending means timing is still computing and the caller should retry in ~15s; unavailable means no timing exists (instrumentals, some engines) and the agent should fall back to songs[].lyrics. That is both a retry policy and a named alternative.

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.