Skip to main content
Glama

skillporter_status

Read-only

Return a unified workspace snapshot of managed, unmanaged, orphaned, drifted, and per-harness skill states to audit coverage and drift.

Instructions

[READ] Return the unified workspace environment snapshot (managed, unmanaged, orphaned, drifted, and per-harness skill states).

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

Input Schema

NameRequiredDescriptionDefault
pathNo.
scopeNoproject

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?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the scope of the snapshot (including drifted and orphaned states), which is useful context, but says nothing about cost, size, refresh behavior, or what a snapshot call actually touches on disk. Incremental value beyond annotations is modest.

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?

A single well-formed sentence with the read tag front-loaded and the payload contents enumerated. No waste, though the bracketed tag is a thin substitute for real usage framing.

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?

With no output schema, the description is the only place return values are characterized, and the category enumeration partially does that job. However, for a tool whose entire value is a structured snapshot, the absence of any parameter explanation or shape hint leaves it only partly complete.

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% for both parameters, so the description must compensate and does not. Neither the meaning of "path" (workspace root?) nor the effect of "scope": project vs user (which environments get scanned) is explained anywhere, leaving an agent to guess the semantics of a defaulted path of ".".

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 ("Return") and resource ("unified workspace environment snapshot"), and enumerates the snapshot's contents (managed, unmanaged, orphaned, drifted, per-harness states). It does not distinguish this from look-alike siblings such as skillporter_inspect, skillporter_diagnose, or skillporter_detect, so an agent cannot route between them from the definition alone.

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?

The only usage signal is the "[READ]" tag, which implies a non-mutating call. There is no statement of when to choose this over skillporter_inspect, skillporter_diagnose, or skillporter_context, and no prerequisites or exclusions are given.

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