Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

recommend_dj_media

Read-onlyIdempotent

Compare selected DJ models and Windows/macOS hosts to recommend a shared filesystem only when every model and host confirms support, preserving unknowns and per-file limits; no device formatting.

Instructions

Compare selected DJ models and Windows/macOS preparation hosts. Recommend a shared filesystem only when each selected model and host has confirmed support; preserve unknowns and per-file limits. Does not format a device.

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": {
      "models": "<models>"
    },
    "name": "recommend_dj_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsYes
host_platformsNo
firmware_versionsNo
rekordbox_versionNo
largest_file_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description still adds genuine behavioral context: the gating semantics (no recommendation without confirmed support) and the explicit non-action ("Does not format a device"), which prevents an agent from assuming side effects.

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?

Three short sentences, front-loaded with the comparison and followed by the gating rule and the negative scope. Nothing is wasted, though phrases like "per-file limits" are compressed to the point of ambiguity.

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 read-only advisory tool with no output schema, the description conveys the decision logic but not the shape of the recommendation or how the nested firmware_versions map influences it. With 0% schema coverage on 5 parameters, an agent must guess at several inputs.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description bears full responsibility. It alludes to models, host platforms (Windows/macOS) and a per-file size limit, but leaves firmware_versions and rekordbox_version completely unexplained, including whether the Rekordbox version constrains the recommendation.

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 names a specific verb+resource pair ("Compare selected DJ models and Windows/macOS preparation hosts") and states the produced artifact (a shared-filesystem recommendation). The closing "Does not format a device" carves it away from the formatting/write siblings, though it never contrasts with close neighbors like filesystem_compatibility or dj_model_compatibility.

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?

It gives a decision rule for when a recommendation is emitted ("only when each selected model and host has confirmed support") plus the conservative fallback ("preserve unknowns"). But it says nothing about when to call this versus the sibling compatibility/advice tools, and no prerequisites are stated.

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