Skip to main content
Glama

Open Mix in Dizko ID

open_mix_in_dizko_id
Read-onlyIdempotent

Use this when a user wants the tracks in a DJ mix identified or bought. Checks a SoundCloud mix link and returns the hand-off to Dizko ID, the Chrome extension that finds the tracks and fills their Beatport or Bandcamp cart. This tool identifies nothing.

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": {
      "mix_url": "<mix_url>"
    },
    "name": "open_mix_in_dizko_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
mix_urlYesSoundCloud mix link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description's job is to add context. It adds a meaningful detail those annotations do not contain: the tool performs no identification itself and instead hands off to an external Chrome extension, which sets the user's expectations for what comes back. It doesn't describe the shape of the returned hand-off, which leaves a small gap.

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?

Three short sentences, with the trigger condition first, the mechanism second, and the key limitation last. Every sentence carries information, and there is no redundant phrasing.

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-only hand-off tool with no output schema, this description covers the trigger, the mechanism, and the limitation. The only real gap is that it does not say how the hand-off is delivered (such as a URL or a deep link). That is minor, but an agent might still want it.

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?

There is a single required parameter with 100% schema description coverage, so the schema already fully documents it. The description only repeats 'SoundCloud mix link' and adds nothing about URL formats or validation beyond that. The baseline of 3 fits when the schema does all the work and the description adds no extra meaning.

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 states a specific verb and resource: it checks a SoundCloud mix link and returns a hand-off to Dizko ID, the Chrome extension that finds tracks and fills a Beatport or Bandcamp cart. It also explicitly rules out an adjacent capability with 'This tool identifies nothing,' so an agent knows exactly what this call produces.

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?

It gives a concrete trigger condition: 'Use this when a user wants the tracks in a DJ mix identified or bought.' It also supplies a negative boundary ('identifies nothing'), but it does not name any alternative tool or say what to call when the user does not want identification or purchase.

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.

Resources