Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_multi_read

Read-onlyIdempotent

Decodes a specified Multi from a Kurzweil SP6 backup file, returning its name plus per-zone settings such as enabled state, channel, program, keys, transpose, volume, and pan.

Instructions

Decode one Multi: name and per-zone enabled/channel/program/keys/transpose (+ read-only volume/pan).

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": {
      "path": "<path>",
      "multi_id": "<multi_id>"
    },
    "name": "sp6_multi_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
multi_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/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 a closed-world scope, so the safety profile is covered. The description adds what the caller gets back (a decoded per-zone view plus read-only volume/pan), which is genuine added value, but it says nothing about failure behavior when multi_id or path is invalid.

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?

A single front-loaded sentence with no filler. It is dense to the point of being cryptic in the parenthetical "+ read-only volume/pan", but nothing is wasted.

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?

With no output schema, the description usefully enumerates the returned fields, which is the most important gap for a decoder. However, for a two-parameter tool with zero schema documentation, it leaves the meaning of path entirely unstated and gives no hint about error or empty-case behavior.

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%, so both parameters carry no documented meaning in the schema and the description must compensate — it does not. It never explains what "path" refers to (a file, a directory, a project root) or what form multi_id takes, leaving only the weak hint that "one Multi" is selected by multi_id.

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?

"Decode one Multi" gives a specific verb and resource and enumerates the decoded content (name, per-zone enabled/channel/program/keys/transpose, volume/pan). That is enough to tell it apart from sp6_multi_build and sp6_multi_validate, though the description never names those siblings as alternatives.

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-to-use guidance. The verb "decode" and the phrase "one Multi" imply reading a single existing Multi, but the agent must infer that sp6_multi_validate or sp6_multi_build are the wrong picks for inspection.

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