Skip to main content
Glama
Sign In

Lyrics Ovh

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Suggest

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": "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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "bohemian rhapsody"
+  },
+  {
+    "limit": 5,
+    "query": "love songs"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of track suggestions with artist info",
+      "items": {
+        "properties": {
+          "artist": {
+            "description": "Artist information",
+            "type": "object"
+          },
+          "title": {
+            "description": "Song title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of suggestions available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "data"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "bohemian rhapsody"
-  },
-  {
-    "limit": 5,
-    "query": "love songs"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "data": {
-      "description": "Array of track suggestions with artist info",
-      "items": {
-        "properties": {
-          "artist": {
-            "description": "Artist information",
-            "type": "object"
-          },
-          "title": {
-            "description": "Song title",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total": {
-      "description": "Total number of suggestions available",
-      "type": "number"
-    }
-  },
-  "required": [
-    "total",
-    "data"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "bohemian rhapsody"
+  },
+  {
+    "limit": 5,
+    "query": "love songs"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of track suggestions with artist info",
+      "items": {
+        "properties": {
+          "artist": {
+            "description": "Artist information",
+            "type": "object"
+          },
+          "title": {
+            "description": "Song title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of suggestions available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "data"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds minimal behavioral context (returning track+artist info) beyond the annotations. No contradictions.

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?

The description is a single 12-word sentence, highly concise and front-loaded. It could be slightly more structured (e.g., bullet points) but is efficient.

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?

With an output schema present, return values are documented. The description covers input (free-form query) and output (track+artist info) adequately for a simple suggestion tool. Could mention scope or edge cases, but it's generally sufficient.

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 50% (only 'limit' has description). The description explains 'query' as 'free-form query', adding some context, but does not elaborate on 'limit' beyond its schema description. Baseline 3 is appropriate given partial coverage.

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 clearly states the verb ('suggest'), the resource ('Title/artist suggestions'), and the input context ('free-form query'), while also noting the output includes track and artist info. This effectively distinguishes it from sibling tools like 'lyrics' or 'search_within'.

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

Usage Guidelines3/5

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

The description implies usage for open-ended music queries but does not explicitly state when to use this tool versus alternatives (e.g., 'lyrics' for lyrics, 'search_within' for other searches). No exclusions or when-not-to-use guidance is provided.

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

All Lyrics Ovh toolsInspect
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.

Resources