Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_multi_build

Writes a new Multi file into the artifacts directory without modifying the template or keyboard. Outputs .ksp6 or .fmlt, leaving user Programs out and flagging partial exports.

Instructions

Write a NEW Multi file inside the artifacts directory. Never touches the template or the keyboard.

output_path is relative to the artifacts directory, must not exist and must end with .ksp6 or .fmlt matching output_format. 'ksp6' (default) is a complete copy of the template bank with the new Multi in one empty record; 'fmlt' follows the editor layout (Multi, then each zone's Program with its FX/algorithm records); user Programs are left out and flagged PARTIAL_EXPORT.

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": {
      "spec": "<spec>",
      "output_path": "<output_path>"
    },
    "name": "sp6_multi_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
output_pathYes
output_formatNoksp6

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the no-overwrite policy ('must not exist'), the no-side-effect guarantee on the template and keyboard, and a real lossiness caveat: in fmlt mode user Programs are omitted and flagged PARTIAL_EXPORT. That lossy-export warning is exactly the kind of consequence an agent needs before invoking, and it is consistent with destructiveHint=false.

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?

Front-loaded with the action and its safety guarantee in the first sentence, then preconditions, then format semantics. Dense but every clause carries information; the parenthetical format breakdowns are long yet necessary given that the enum has no schema descriptions.

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?

There is no output schema and no statement of what the call returns (path, diff, validation result), and the nested 'spec' structure is entirely unaddressed for a mutation tool. The write-side behavior is well covered, but an agent still cannot construct the primary input or anticipate the response shape.

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%, but the description compensates well for output_path (relative to artifacts dir, must not exist, extension must match format) and output_format (what each enum value produces). However the required 'spec' parameter, a nested free-form object with additionalProperties=true, gets no explanation at all, leaving the core input undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Write) and resource (a NEW Multi file) with an explicit scope (inside the artifacts directory), plus a negative guarantee ('Never touches the template or the keyboard') that separates it from read/validate siblings. An agent can tell this is the creation path rather than an inspection path without opening the schema.

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

Usage Guidelines4/5

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

Preconditions are explicit: output_path must not exist and must end with .ksp6 or .fmlt matching output_format. It also explains which format to pick ('ksp6' default bank copy vs 'fmlt' editor layout). It stops short of naming an alternative tool (e.g., sp6_multi_read for existing files) or stating when-not to call it, so not a 5.

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