Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_spec_schema

Read-onlyIdempotent

Provides the JSON Schema for the setting sheet accepted by Multi validation and build operations, helping you format configuration input correctly before validating or generating SP6 Multi files.

Instructions

JSON Schema of the setting sheet accepted by sp6_multi_validate / sp6_multi_build.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only the purpose and the consumer tools, not whether the schema is static or how large/structured the returned document is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; every element (what is returned, for which tools) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, read-only schema lookup with no output schema, the description identifies the returned artifact and its consumers, which is what an agent needs. Minor gap: it does not state that the schema is stable/static or hint at its structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a 0-param tool applies. The description correctly adds no noise about arguments.

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 names the specific artifact returned (the JSON Schema of the setting sheet) and ties it to the two sibling tools that consume it, so an agent can distinguish it from sp6_multi_validate and sp6_multi_build themselves. It stops short of a 5 because it is a noun phrase rather than an explicit 'returns the schema' statement.

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?

Naming sp6_multi_validate and sp6_multi_build gives clear context: this is the discovery step for their shared input format. There is no explicit 'call this first' instruction or exclusion, but the consumer relationship is unambiguous.

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