Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_multi_validate

Read-onlyIdempotent

Validates a setting sheet against its template and reports all errors and warnings at once, including field paths, effective zones, and sounding note ranges.

Instructions

Check a setting sheet against its template file and report every problem at once.

Returns valid / can_build, errors and warnings with field paths, the effective zones (sheet over template) and sounding note ranges.

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>"
    },
    "name": "sp6_multi_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare this to be a safe, idempotent, closed-world read, so the description's obligation is to add behavioral detail, and it does: it promises a full report of all problems, not just the first, and names the specific outputs (valid, can_build, errors, warnings with field paths, effective zones, sounding note ranges). It does not say how template overrides or precedence failures are reported.

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?

The description is two sentences with no wasted text, and the action and its result are stated first, followed by the enumerated outputs. The line break makes the return-value list readable without padding.

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?

The return shape is described in prose, and there is no output schema to cover it. However, this tool accepts a nested free-form object with zero schema documentation, so the biggest thing an agent needs (what to put in spec) is entirely absent and cannot be inferred from the schema.

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?

There is a single required parameter, the spec, which is a free-form object with additionalProperties and 0% schema description coverage. The description only hints that the spec carries a setting sheet and a template, but it never explains the expected keys, how the template is referenced, or what a malformed spec triggers.

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?

The description gives a specific verb and resource: it checks a setting sheet against its template file and reports every problem at once, which sets it apart from the mutating sibling sp6_multi_build. It stops short of naming an alternative for the case where the caller wants to fix problems rather than list them.

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?

The phrase 'against its template file' and 'report every problem at once' imply that this tool is a pre-flight or audit step, but no explicit when-to-use, when-not-to-use, or alternative (such as build or diff) is stated. Guidance is inferable rather than given.

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