Skip to main content
Glama

skill_health

Check whether installed skills are actually used across agents: invocations, last use, missed triggers, outcome signals, and a keep, revise, update, or retire recommendation.

Instructions

Check how your installed skills are actually used across agents: invocations per agent, last use, missed triggers (matching work where the skill never fired, meaning its description needs work), outcome proxies, references to commands that no longer appear, and a keep / revise / update / retire call.

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

Input Schema

NameRequiredDescriptionDefault
projectNo
days_backNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Check' implies a read-only audit and the enumeration of outputs (invocations, last use, missed triggers, outcome proxies) gives real insight into what is computed. However, it does not state data sources or lookback bounds, whether the analysis is expensive/slow, or that results are advisory only, leaving notable behavioral gaps.

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 front-loaded sentence with a colon-delimited enumeration; each listed signal earns its place by telling the agent what the report contains. The nested parenthetical about missed triggers is slightly clunky but not wasteful.

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?

The output side is well covered by both the enumeration and the existing output schema, so return values need no further explanation. The gaps are on the input side: two undocumented parameters and no annotation-driven safety profile mean an agent can invoke it but not reason precisely about scope or cost.

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 two parameters, and the description never mentions either 'project' or 'days_back'. The default 60-day window and the meaning of project scoping are left entirely undocumented, so an agent must guess what window and scope its audit covers.

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 and resource ('Check how your installed skills are actually used across agents') and enumerates the concrete signals produced: invocations per agent, last use, missed triggers, outcome proxies, stale command references, and a keep/revise/update/retire call. The purpose is unambiguous, but it never names a sibling such as analyze_sessions or suggest_skills to differentiate the scope.

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: the parenthetical about missed triggers meaning 'its description needs work' hints that this is an audit-before-revising tool, but there is no explicit statement of when to call it versus analyze_sessions or suggest_skills, and no preconditions such as required history or installation state.

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