Fetch the folder and file structure of the entire project, or narrow to a specific module when provided, to give an architecture overview while reducing token consumption.
Devuelve la estructura de carpetas y archivos. Si no se indica 'module', devuelve la estructura completa de todo el proyecto.
| Name | Required | Description | Default |
|---|---|---|---|
| module | No | Nombre opcional del módulo o subproyecto (ej: 'dayone-api', 'dayone-front', 'core', etc.). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the key behavioral trait: omitting 'module' returns the full project structure. However, it doesn't mention whether this is a read-only operation, performance implications, or what the output format looks like. For a read-only structure tool, this is adequate but not rich.
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?
Two sentences, front-loaded with the core purpose, and the conditional behavior is stated efficiently. No wasted words.
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 read-only tool with one optional parameter and no output schema, the description is mostly complete. It explains the main behavior and the parameter's effect. It could mention the output format or that it's read-only, but given the simplicity, this is sufficient.
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 documents the 'module' parameter. The description adds the behavioral meaning: if not provided, full structure is returned. This adds value but doesn't go beyond what the schema plus the main description already imply.
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 clearly states the tool returns the folder and file structure, and specifies the scope behavior when 'module' is not provided. It distinguishes itself from list_modules by focusing on structure rather than module listing, though it doesn't explicitly name the sibling.
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 gives clear context: use it to get the project structure, and optionally narrow to a module. It implies the alternative list_modules is for listing modules, but doesn't explicitly state when to use one over the other. The conditional behavior is clearly explained.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.