Skip to main content
Glama

skillporter_diff

Read-only

Compare workspace skills and configuration against a workspace-relative .skillpack archive or directory to find drift and mismatches.

Instructions

[READ] Compare the workspace environment against a workspace-relative .skillpack archive or 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": {
      "target": "<target>"
    },
    "name": "skillporter_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
targetYesWorkspace-relative .skillpack file, dir, or profile:<name>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.1/5.0
Behavior3/5

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

The [READ] tag and 'Compare' wording are consistent with the readOnlyHint=true annotation, and the description adds useful context about what is being compared. However, it does not disclose return behavior, handling of missing targets, or any limits, so it adds only moderate value beyond the annotations.

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?

The description is a single front-loaded sentence with no wasted wording. The [READ] marker is placed first, followed immediately by the verb and scope.

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 simple read-only comparison tool with annotations covering safety, the core purpose is clear. Still, the undocumented 'path' parameter and the lack of any hint about output format leave meaningful gaps given there is no output 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?

Schema description coverage is only 50%, and the description does not compensate: the 'target' parameter is already documented in the schema, while the 'path' parameter is neither described in the schema nor explained in the description. The description adds no parameter meaning beyond what the schema already provides for target.

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 a clear resource: the workspace environment versus a workspace-relative .skillpack archive or directory. It is understandable without opening the schema, though it does not explicitly differentiate itself from siblings like inspect, detect, or diagnose.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites, and no when-not conditions. The comparison scope implies a diff-style use case, but the description leaves routing entirely to inference despite many sibling tools.

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