Skip to main content
Glama

skillporter_insights

Read-only

Measure estimated token overhead for skills and instruction files, detect duplicate copies, and report local opt-in usage insights to audit workspace AI agent skills.

Instructions

[READ] Measure estimated token overhead of skills and instruction files, detect duplicates, and report local opt-in usage insights.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile, and '[READ]' merely restates it. The description does add genuine behavioral context beyond annotations: 'estimated' token overhead signals approximate rather than exact numbers, and 'local opt-in usage insights' signals local-only, consent-based telemetry. It does not say whether insight collection must be enabled for results to appear, nor how the three outputs are combined.

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?

One sentence, front-loaded with the '[READ]' marker, with no filler or repetition. It is efficient, though packing three distinct capabilities into a single clause makes it slightly harder to parse than a short structured list would be.

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?

There is no output schema, so the description carries the burden of explaining the return shape, and it does not — an agent cannot tell whether token overhead, duplicates, and usage insights always come back together or which one dominates the response. Combined with the undocumented path parameter, this leaves meaningful gaps for a multi-purpose analysis tool, though the annotations cover the safety dimension.

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?

The single 'path' parameter has 0% schema description coverage and is never mentioned in the description. The agent cannot tell whether path points at a file, a skill directory, or a workspace root, or what the default '.' scans. With one undocumented parameter, the description was the only place to compensate and does not.

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 names three concrete capabilities with specific verbs and resources: measuring estimated token overhead of skills/instruction files, detecting duplicates, and reporting local opt-in usage insights. An agent knows what output to expect. It stops short of a 5 because there is no differentiation from closely related siblings like detect, scan, inspect, or diagnose, so the boundary of this tool's purpose is unclear.

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 when-to-use statement, no exclusion, and no named alternative, despite a crowded sibling set containing detect, scan, inspect, diagnose, and matrix. The '[READ]' prefix only implies read-only usage that annotations already convey. The agent must guess whether this is a one-shot summary tool or overlaps with the other analysis tools.

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