Skip to main content
Glama
@skills-hub-ai/mcp

@skills-hub-ai/mcp

list_installed_skills

Lists locally installed Claude Code and Cursor skills by scanning their skill directories, so compatible AI clients can discover and use available SKILL.md prompts.

Instructions

List all locally installed skills

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, but the tool is a zero-parameter local read with low risk. It states that ALL installed skills are returned, implying no pagination or filtering, yet says nothing about what each entry contains, whether the result is cached, or whether uninstalled/disabled skills appear.

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 six-word sentence that front-loads the verb and resource with no filler or redundancy. It is appropriately sized for a zero-parameter list operation.

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 simple enumeration tool this is minimally viable, but with no output schema the description should say what a returned 'skill' looks like (name only vs. metadata) so an agent knows whether it needs get_skill_detail afterward. That is the one remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object, so there are no parameters whose meaning could be clarified. Baseline for a zero-parameter tool applies, and the description correctly signals the tool takes no filtering arguments.

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 gives a specific verb ('List') and resource ('locally installed skills'), with a scope qualifier that separates it from a catalog-wide search. It does not explicitly name the sibling search_skills, so differentiation is inferred rather than stated, but an agent can still tell what this returns.

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 or when-not-to-use guidance and no mention of alternatives: nothing says to prefer this over search_skills for enumerating what is already present, or to use get_skill_detail for specifics. The local-vs-catalog distinction is only implicit in the word 'locally'.

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