Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

smart_media_plan

Read-onlyIdempotent

Recommend offline USB media plans for DJ gear by checking device eligibility, firmware, host platform, file-size limits, library type, and sourced formatting guidance; show uncertainty; never format.

Instructions

Quick offline rule-based media recommendation combining actual USB eligibility, destination DJ equipment, firmware, preparation platforms, individual-file limits, library types and sourced formatting guidance. Shows uncertainty and never formats a device.

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": "smart_media_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelsNo
purposeNodj
device_numberNo
host_platformsNo
file_size_classNounknown
partition_schemeNoauto
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
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value with 'offline', 'shows uncertainty', and 'never formats a device', but with no output schema it says nothing about what the recommendation response contains or how uncertainty is surfaced.

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 sentences, front-loaded with the core action and scope, with no filler. The long noun list is dense but each item corresponds to a real input domain, so it earns its space.

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 9-parameter, nested-object tool with no output schema, the description covers inputs conceptually and the safety posture, but omits any indication of the return shape or how the recommendation is structured. An agent can decide to call it but cannot anticipate the result.

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 description coverage is 0% across 9 parameters, so the description must compensate. It enumerates the input domains (USB eligibility, DJ equipment, firmware, host platforms, file limits, library types, formatting guidance), which maps loosely onto models, firmware_versions, host_platforms, file_size_class and purpose, but leaves device_number, partition_scheme, rekordbox_version and largest_file_bytes unexplained.

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 specific verb and resource ('rule-based media recommendation') and scopes it as offline and advisory, with 'never formats a device' distinguishing it from the write/format siblings. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

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?

'Quick offline rule-based' and 'never formats a device' imply this is the advisory/pre-flight choice rather than an execution tool, which is useful context. However, it never says when to prefer it over dry_run_usb_plan or recommend_dj_media, nor any prerequisites, so the agent must guess among several plausible alternatives.

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