agentskills-mcp

List Skill References

list_skill_references

Lists files in a skill's references directory so agents can locate supporting documents and assets before fetching them.

Instructions

List files in a skill's references/ directory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_id": "<skill_id>"
    },
    "name": "list_skill_references"
  }
}

Input Schema

Name	Required	Description	Default
`skill_id`	Yes	Directory name of the skill.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Nov 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it adds little beyond the verb. It does not say that listing is read-only and side-effect free, what happens if the skill has no references/ directory, whether subdirectories are included, or whether results are ordered or paginated. The existence of an output schema covers return values but not these edge-case behaviors.

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 short sentence with zero filler and the resource qualifier front-loaded. It is efficient, though slightly under-specified rather than overly verbose, so nothing needs trimming.

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 one-parameter read/list tool with a full output schema, the description is functional but thin. It never connects to the sibling get_skill_reference or explains the empty-directory case, leaving gaps that structured fields do not fill.

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 coverage is 100% with a single parameter that is already documented as "Directory name of the skill." The description adds only the framing that this ID selects the skill whose references/ directory is listed, which is marginal beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ("List") and resource ("files in a skill's references/ directory"), and the directory qualifier separates it from list_skill_scripts and list_skill_assets. It does not explicitly name those siblings, but the scoping is precise enough that an agent can pick it over get_skill_reference for enumeration.

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: enumerate references before fetching one with get_skill_reference, or when you need to know which reference files exist. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the workflow from the sibling names.

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

Deploy Server