Lists available dataset templates for shared, config, _domain-slice, authorization, or all, helping agents choose the right scaffold when generating NestJS hexagonal services.
Lista las plantillas disponibles en el dataset (shared, config, _domain-slice).
| Name | Required | Description | Default |
|---|---|---|---|
| subdir | No | Subconjunto del dataset a listar. | all |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. "Lista" implies a read operation, but the description does not state read-only status, permissions, pagination, return format, or any other operational context.
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?
The description is a single front-loaded sentence with no wasted words. The parenthetical example list is compact, though it is incomplete relative to the schema enum.
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 one-parameter list tool, the description is minimally adequate. However, with no annotations or output schema, it could better explain return behavior, and its subset examples omit two schema enum values including the default all.
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?
Schema description coverage is 100%, so the schema already defines the subdir parameter and its enum values. The description mentions three subsets parenthetically but does not add meaning beyond the schema, and omits the authorization and all enum values.
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 ("Lista") and resource ("plantillas") and scopes it to the dataset. It implicitly distinguishes itself from get_template by focusing on listing rather than fetching a single template, but it does not name any sibling explicitly.
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?
There is no explicit guidance on when to use this tool versus alternatives such as get_template. The listing intent is implied, but no conditions, prerequisites, or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.