skills_listList available guidance playbooks for using the book-recommendations server effectively. Find and read skill guides to optimize your experience.
List available skills (guidance playbooks) for using this server well — read one with skill_read
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds meaningful context by defining what skills are (guidance playbooks) and their purpose (using the server well). It does not contradict annotations and provides useful domain context beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the core action ('List available skills'), immediately defines the resource, and ends with an actionable pointer to the sibling tool. Every word earns its place; there is no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless, read-only listing tool, the description is complete. It tells the agent what the tool returns (a list of skills), what those skills are, and how to proceed (skill_read). No output schema exists, but the simplicity makes that acceptable. The annotations cover safety, so nothing is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is nothing to document. Per the rubric, a baseline of 4 applies for 0 params. The description adds no parameter information because none exists, and the schema correctly shows an empty properties object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and a resource ('available skills'), clarifies they are 'guidance playbooks', and directly distinguishes from the sibling tool skill_read by pointing to it as the next step. This is a precise, unambiguous purpose statement.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent when to use this tool (to see the list of skills) and when to use the alternative skill_read ('read one with skill_read'), providing clear routing between the two related tools. This matches the standard of the get_calls example.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.