Skip to main content
Glama

skill_list

Lists markdown and script files from agent-skill repositories cloned into ./skills-repos, with an optional substring filter on relative paths to locate relevant skills quickly.

Instructions

List markdown/scripts of the agent-skill repositories cloned into ./skills-repos (see scripts/fetch-skills.sh).

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

Input Schema

NameRequiredDescriptionDefault
filterNoSubstring filter on the relative path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the data source (./skills-repos) and the prerequisite clone script, but does not state whether the operation is read-only, what happens if the directory is missing, or what the listing output looks like.

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?

The definition is a single front-loaded sentence with no filler. The parenthetical reference to the fetch script earns its place by explaining where the repositories come from, though the sentence could be slightly clearer about output shape.

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 one-parameter listing tool with no output schema, the description covers the data source and setup prerequisite. It still leaves gaps around output format, empty-directory behavior, and whether markdown and scripts are listed together or separately.

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

Parameters3/5

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

Schema description coverage is 100%, so the filter parameter is already fully documented in the schema as a substring filter on the relative path. The description adds no additional parameter meaning, which is acceptable given the high schema coverage baseline.

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 states a clear verb (List) and resource (markdown/scripts of agent-skill repositories), plus the source directory ./skills-repos. It does not explicitly contrast with sibling skill_read, but an agent can tell it is a listing operation rather than a read operation.

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 reference to scripts/fetch-skills.sh implies the repositories must be cloned first, which is useful setup context. However, there is no explicit guidance on when to use this instead of skill_read or other catalog/search siblings, and no exclusions or alternatives are named.

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