Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

check_dj_audio

Read-onlyIdempotent

Verify a DJ audio file's actual codec, sample rate, and bit depth against exact-model manufacturer requirements, while preserving unknown rates and flagging ambiguous M4A codec cases.

Instructions

Check an actual audio codec and optional sample rate/bit depth against exact-model manufacturer evidence. Preserves unknown/non-exhaustive rates and firmware conditions; M4A alone is ambiguous between codecs.

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>",
      "format": "<format>"
    },
    "name": "check_dj_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
formatYes
bit_depthNo
sample_rate_hzNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation, so the description need not restate safety. It adds useful behavior beyond the annotations: unknown/non-exhaustive rates and firmware conditions are preserved, and M4A is noted as ambiguous between codecs. It still does not describe the response shape or what 'preserved' means concretely.

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?

Two sentences, front-loaded with the core purpose and followed by a compact edge-case note; there is no filler. The dense phrasing is terse rather than verbose.

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?

The description covers the core check and some edge-case behavior, which is enough to invoke the tool. However, with no output schema it omits what the check returns (e.g., boolean/evidence structure), and it gives no workflow guidance relative to sibling tools. For a four-parameter validation tool, those are meaningful gaps.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must supply parameter meaning. It does identify model as the exact model for manufacturer evidence, format as the audio codec, and sample rate/bit depth as optional inputs, with M4A as an example codec. It does not define accepted format values or model-string syntax, so some semantic gaps remain.

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?

Uses a specific verb ('Check') and names the resources: audio codec plus optional sample rate/bit depth, checked against exact-model manufacturer evidence. It is distinguishable from generic equipment-detection siblings, but it does not explicitly name a sibling or state when that sibling should be used instead.

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 a validation/compatibility-check use case ('against exact-model manufacturer evidence') but gives no explicit when-to-use, prerequisites, or alternatives. An agent can infer this is for verifying a model/format combination, but the routing guidance is thin.

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