Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

list_dj_models

Read-onlyIdempotent

List manufacturer-sourced DJ equipment models to verify catalog coverage. Note that an absent model is unconfirmed rather than unsupported, so check before assuming compatibility.

Instructions

List the bounded manufacturer-sourced DJ equipment catalog. An absent model is unconfirmed, not necessarily unsupported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dj_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds genuine context beyond them: the catalog is finite, manufacturer-sourced, and incomplete, meaning a miss is inconclusive rather than a negative signal. It does not say how the results are ordered, whether the list is cached/static, or how large it is.

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 tight sentences with no filler, and the scope qualifier is front-loaded in the first sentence. It is efficient, though the second sentence's caveat is the only substantive addition — the definition is arguably too terse for a tool with an undocumented filter parameter.

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

Completeness2/5

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

There is no output schema, so the description should carry the burden of describing return shape, yet it says nothing about what a result entry contains or how many items come back. Combined with an entirely undocumented `query` parameter, an agent can call the tool but cannot predict filtering behavior or the structure of the response.

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% for the single optional `query` parameter, and the description never mentions it at all — no indication of what it matches (model name, manufacturer, partial tokens), whether it is case-insensitive, or what an empty default returns. With the only parameter undocumented in both schema and description, an agent must guess at filtering semantics.

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?

States a concrete verb and resource ("List ... DJ equipment catalog") and narrows the scope with "bounded manufacturer-sourced," which tells an agent this is a curated static inventory rather than a live detection scan. It never names a sibling (e.g. detect_dj_equipment, dj_model_compatibility), so the distinction from those tools has to be inferred from the wording alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance and no named alternative, despite several siblings that could plausibly overlap (detect_dj_equipment, dj_model_compatibility). The caveat about absent models is guidance on interpreting results, not on selecting this tool over another, so selection support is effectively absent.

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