Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_artifact_diff

Read-onlyIdempotent

Compare a source template with a generated SP6 artifact to verify records and decoded Multi fields, helping catch configuration mismatches before use.

Instructions

Compare a template/source file with a generated file (records and decoded Multi fields).

artifact_path may be relative to the artifacts directory.

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": {
      "source_path": "<source_path>",
      "artifact_path": "<artifact_path>"
    },
    "name": "sp6_artifact_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_pathYes
artifact_pathYes
source_multi_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description adds nothing beyond that. With no output schema, the agent is left unaware of what a diff response contains, how discrepancies are reported, or what happens when files fail to match.

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

Conciseness3/5

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

The text is short and front-loads the comparison before the path note, but the second sentence is a fragment and the parenthetical about records/decoded Multi fields is unexplained jargon that does not earn its place.

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?

For a three-parameter tool with zero schema descriptions and no output schema, the description is thin: it omits the meaning of source_multi_id and gives no sense of the result shape or mismatch semantics. An agent could invoke it but would not know how to interpret what comes back.

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% across three parameters, so the description must carry the load. It only clarifies that artifact_path may be relative to the artifacts directory, leaving source_path and especially source_multi_id (an optional integer) entirely unexplained.

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 states a specific verb (compare) and two specific resources (a template/source file versus a generated file), so an agent can tell the operation is a diff. It does not differentiate from related siblings such as sp6_multi_validate or sp6_file_inspect, and the parenthetical '(records and decoded Multi fields)' adds domain jargon rather than sharpening the purpose.

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 guidance on when to run a diff versus validate or inspect a Multi, and no prerequisites are stated. The only usage-adjacent sentence concerns path resolution for one parameter, not tool selection.

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