oh-my-cassette

Overview Schema Source Related Servers Score Discussions Admin

cassette_jamendo_setup

Validate and privately store your Jamendo Client ID for read-only music matching. No Client Secret required; failed validation keeps existing config.

Instructions

Validate and privately store this machine's own Jamendo Client ID for read-only music matching. Before calling, explain that the user creates a read-only application at https://devportal.jamendo.com/, no Client Secret is needed, and pasting the Client ID places it in the conversation transcript. Ask for their Client ID; never invent one and never ask for a Client Secret. A failed validation preserves existing configuration.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`client_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`phase`	Yes
`job_id`	No
`warnings`	No
`artifacts`	No
`session_id`	No
`next_action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.19Sep 3, 2026

addedOutput schema / $defs / Artifact / properties / expires_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expires At"
+}

Addedv0.4.16Aug 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and handles it well. It discloses that the tool stores data privately, that matching is read-only, that the Client ID appears in the transcript, that validation failure preserves existing configuration, and that the agent must not fabricate credentials. This is strong behavioral disclosure.

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 front-loaded with the core action and purpose, then adds necessary user-interaction and safety instructions. Every sentence adds meaningful guidance, and it remains compact for the amount of safety-critical context it conveys.

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?

For a simple one-parameter setup tool with an output schema present, the description covers the essential interaction script, privacy concern, failure behavior, and security constraints. Nothing critical is missing for an agent to invoke it correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate. It does: the lone parameter client_id is explained as the user's own Jamendo Client ID, no Secret is involved, and the tool must ask for it rather than invent one. This gives the agent everything needed to handle the parameter correctly.

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 action: validate and privately store this machine's Jamendo Client ID for read-only music matching. It names a specific resource (Client ID), a specific verb (validate/store), and its purpose, which differentiates it from matching or ingestion siblings.

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 description provides explicit step-by-step guidance: explain the read-only application requirements, warn about transcript exposure, ask for the Client ID, and never invent or request a Client Secret. It does not explicitly name alternative tools or state when not to use this tool, but the setup context is clear.

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

Install Server