Inspect a device's full structure: recursive rack chains, chain mixer state, and populated Drum Rack pads.
Read recursive rack chains, native chain mixer state, and populated Drum Rack pads for one device.
| Name | Required | Description | Default |
|---|---|---|---|
| trackId | Yes | Stable device-owner ID: track-N from list_tracks, return-N from get_set_mixer, or master. | |
| deviceId | Yes | Stable device ID returned by list_devices. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds value by specifying exactly which components are read (rack chains, chain mixer state, drum pads), which is beyond a generic 'read' statement and gives the agent a clear picture of what to expect. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, tightly worded sentence that front-loads the verb and enumerates the returned data. Every word contributes to meaning; there is no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
As a read tool with no output schema, the description adequately conveys the purpose and the kind of data returned. It doesn't explicitly mention the return structure (e.g., JSON nesting) or any prerequisites, but given the specific components named and the read-only annotations, an agent has enough context to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: both trackId and deviceId are fully described with origins and examples. The description adds no additional parameter-specific information, so the baseline of 3 applies. It doesn't clarify how the parameters are used beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Read') and resource (device hierarchy) and enumerates the exact data categories: recursive rack chains, native chain mixer state, and populated Drum Rack pads. This is clear and differentiates from sibling tools like list_devices (which only lists devices) and get_producer_chain_blueprint (which relates to blueprints, not state).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: if you need the rack chain structure, mixer state, or drum pad contents of a single device, use this tool. However, it does not explicitly state when to prefer it over alternatives or mention any exclusions. No sibling tool is referenced or contrasted.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.