Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_capabilities

Read-onlyIdempotent

Reports supported file formats, writable Multi fields with evidence, and device support to clarify what the server can and cannot do.

Instructions

What this server can and cannot do: file formats, writable Multi fields with evidence, device support.

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.3/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 openWorldHint=false, so the safety profile is fully covered by structured data. The description adds content-level context -- the three domains it reports on and the phrase 'with evidence', implying backed claims rather than marketing text. It stops short of saying whether results reflect live server state or static docs, or what the response shape is (no output schema exists to compensate).

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 sentence, front-loaded with the core scope ('what this server can and cannot do') followed by the three topic areas. Nothing is redundant. It is a noun-phrase fragment rather than prose, which is terse but still readable, and no sentence 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?

For a zero-parameter, zero-output-schema introspection tool, the description gives the topic list but not the return form, and does not state the key operational fact that this is a discovery entry point for the sp6_* family. Given the complexity is low, it is adequate but leaves the agent to guess how the capabilities are presented.

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?

Zero parameters, so the baseline of 4 applies; there is nothing to document and no ambiguity introduced. The description does not need to explain arguments and correctly omits them.

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?

Names a specific resource (this server's capability surface) and enumerates the concrete topics covered: file formats, writable Multi fields, device support. It is clearly distinguishable from the sibling tools (diff, inspect, build, read, validate, find, spec_schema), none of which enumerate capabilities. The verb is implicit ('what this server can and cannot do') rather than a crisp action verb, which keeps it short of a 5.

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?

The description never says when to call it -- no 'call this first', no 'use before sp6_multi_build if unsure of writable fields', no conditions under which the tool is unnecessary. The only usage signal is indirect: naming 'writable Multi fields' hints it precedes a build, but the agent must infer that. No alternatives are mentioned.

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