Skip to main content
Glama

skillporter_consolidate_preview

Read-only

Preview instruction-file consolidation by discovering agent instruction files and reporting overlap percentage, contradictions, and outdated references without modifying files.

Instructions

[READ] Discover agent instruction files (CLAUDE.md, AGENTS.md, .cursor/rules, copilot-instructions, etc.) and report overlap percentage, contradictions, and outdated file references without modifying files.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'without modifying files'. More importantly, it discloses the return content (overlap percentage, contradictions, outdated file references), which is valuable since no output schema exists. It does not mention recursion depth, performance, or file-count limits.

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 the [READ] marker first, the action and resource next, and the reported outputs last. No filler or redundancy.

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 simple one-parameter read-only tool with no output schema, the description covers purpose, safety, and reported results adequately. The only meaningful gap is the unexplained path parameter and its scoping behavior.

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?

There is one parameter (path, default '.') with 0% schema description coverage, and the description never mentions it. The agent gets no guidance on whether path is a directory root, whether discovery is recursive, or how scope is bounded, so the description fails to compensate for the schema gap.

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?

States a specific verb (discover/report) and resource (agent instruction files), enumerating concrete file types and the three outputs (overlap percentage, contradictions, outdated references). It does not differentiate itself from plausible siblings like skillporter_preview, skillporter_diagnose, or skillporter_scan, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The [READ] tag and 'without modifying files' imply a safe, non-destructive inspection use case, and 'preview' in the name hints at a pre-consolidation check. However, there is no explicit statement of when to choose this over skillporter_preview, skillporter_diagnose, or skillporter_scan, leaving the agent to infer.

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