Skip to main content
Glama

Lyrics Ovh Suggest

lyrics_ovh_suggest
Read-onlyIdempotent

Title/artist suggestions for a free-form query (results have track + artist info).

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": {
      "query": "bohemian rhapsody"
    },
    "name": "lyrics_ovh_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-50 (default 10)
queryYes

Output Schema

NameRequiredDescriptionDefault
dataYesArray of track suggestions with artist info
totalYesTotal number of suggestions available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only that results include track and artist info, which is a small amount of return-content context, and it says nothing about ranking, match quality, or what happens on a no-match query.

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?

A single short sentence with no filler, and the essential information is front-loaded. It is efficient, though the parenthetical is doing structural work that a second sentence could have done more clearly.

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

Completeness2/5

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

With only two parameters and an output schema present, the description could easily have resolved the key ambiguity — what 'suggest' actually returns and how it relates to the 'lyrics' sibling — and it doesn't. For a discovery/selection tool an agent must choose among several similar-sounding tools, this leaves a real decision gap.

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 50%: 'limit' is documented in-schema ('1-50 (default 10)') and 'query' is undocumented but illustrated by examples. The description's 'free-form query' adds a little meaning by signaling natural-language input is accepted, matching the schema baseline of 3 when structured data carries most of the load.

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

Purpose3/5

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

States the resource ('Title/artist suggestions') and input kind ('free-form query'), which is more than a tautology, but 'suggestions' is undefined — it could be autocomplete, fuzzy match, or ranked search. It also fails to distinguish itself from the sibling 'lyrics' tool, so an agent cannot confidently pick between the two from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of when to prefer this over the sibling 'lyrics' lookup, and no prerequisites or exclusions. The agent must infer usage entirely from the name.

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.