Skip to main content
Glama

skillporter_diagnose

Read-only

Diagnose AI agent skill reachability, broken symlinks, SHA-256 content drift, and spec compliance across harnesses in a workspace, revealing broken or drifted skills for audit follow-up.

Instructions

[READ] Diagnose Agent Skill reachability, broken symlinks, SHA-256 content drift, and spec compliance across AI agent harnesses in the workspace.

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

Input Schema

NameRequiredDescriptionDefault
pathNoWorkspace-relative path (default: '.')
scopeNoproject

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.5/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's job is to add context, which it does by naming the four diagnostic dimensions and the cross-harness scope. It does not say whether results are per-harness or aggregated, but the check inventory is substantive beyond the annotation.

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 sentence, front-loaded with the read-only marker and the verb, then a compact enumeration of checks. Nothing is padded and every clause carries information.

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 two-parameter read-only tool with annotations covering safety, this is close to sufficient, but two gaps remain: the `scope` parameter is unexplained in both schema and description, and with no output schema the description never indicates what a diagnosis returns (a report? a list of issues?) or whether any remediation is suggested.

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 coverage is only 50%: `path` is documented in the schema, but `scope` has an enum and default with no explanation of what project vs user means. The description says "in the workspace," which hints at project scope but never explains the parameter or how scope changes the diagnosis.

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 uses a specific verb ("Diagnose") plus a concrete resource, and enumerates the exact conditions checked: reachability, broken symlinks, SHA-256 content drift, and spec compliance. It is clear what the tool does, though it never names a sibling (status, inspect, scan) to sharpen the boundary.

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?

Usage is only implied by the verb "Diagnose" — an agent can infer this is for troubleshooting unhealthy skills, but there is no explicit when-to-use or when-not-to-use guidance. With siblings like skillporter_status, skillporter_inspect, and skillporter_scan present, a routing sentence would materially help.

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