Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

dj_model_compatibility

Read-onlyIdempotent

Check a specific DJ model’s USB filesystem, audio playback limits, library types, and firmware conditions against official sources before preparing media.

Instructions

Read exact-model USB filesystems, audio playback limits, library types and version/firmware conditions, with official sources. Does not certify physical hardware acceptance.

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": {
      "model": "<model>"
    },
    "name": "dj_model_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe read-only, idempotent, non-destructive operation, so the description doesn't need to restate safety. It adds genuine context beyond them: results are grounded in 'official sources' (provenance) and the tool explicitly disclaims certifying physical hardware acceptance, which prevents over-trusting the output.

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?

Two short sentences, front-loaded with the capability before the caveat, with essentially no filler. The dense noun list of covered data types is efficient, though 'with official sources' is slightly awkwardly placed.

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

Completeness3/5

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

For a one-parameter read tool with full annotation coverage and no output schema, the description is adequate but leaves gaps: it doesn't say what shape results take (per-condition verdicts vs. a summary) or how missing/unsupported models are reported.

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 0% for the single 'model' parameter, so the description must carry meaning. It implies the value must be an exact model designator rather than a family or fuzzy match, but gives no format example or guidance on what happens for unknown/unsupported models.

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

Purpose4/5

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

The description opens with a specific verb ('Read') and enumerates the exact resource set: USB filesystems, audio playback limits, library types, and version/firmware conditions. The qualifier 'exact-model' distinguishes it from the broader filesystem_compatibility and rekordbox_version_advice siblings, though it never names those alternatives directly.

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?

Usage is implied rather than stated: the 'exact-model' framing tells an agent to call this when it has a precise model identifier rather than a general compatibility question. The closing exclusion ('Does not certify physical hardware acceptance') clarifies a boundary, but no explicit when-to-use/when-not comparison to sibling tools is given.

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