Lyrics Ovh

Lyrics

lyrics

Read-onlyIdempotent

Exact-name lookup. Returns the lyrics text for an (artist, title) pair.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "Yellow",
      "artist": "Coldplay"
    },
    "name": "lyrics"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	e.g. "Yellow"
`artist`	Yes	e.g. "Coldplay"

Output Schema

Name	Required	Description	Default
`lyrics`	Yes	The full lyrics text for the song

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "artist": "Coldplay",
+    "title": "Yellow"
+  },
+  {
+    "artist": "The Beatles",
+    "title": "Let It Be"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "lyrics": {
+      "description": "The full lyrics text for the song",
+      "type": "string"
+    }
+  },
+  "required": [
+    "lyrics"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety. The description adds the behavioral constraint of exact-name matching, which is not in annotations, thus providing additional transparency.

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

Conciseness5/5

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

The description is extremely concise (one sentence) with no extraneous content. Every word is purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, annotations, and presence of output schema, the description provides all necessary context. Agent can correctly select and invoke the 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 coverage is 100% with clear parameter descriptions. The description only restates 'artist, title pair' without adding new details beyond schema, so baseline score applies.

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 uses specific verb 'returns' and resource 'lyrics text', clearly stating the tool does an exact-name lookup for an artist-title pair. It is unambiguous and sets clear expectations.

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?

The phrase 'Exact-name lookup' implicitly tells the agent when to use this tool (exact match) and when not (fuzzy or partial matches). No explicit alternatives are given, but the context is clear enough.

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

All Lyrics Ovh tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.