List files and directories in a specified path, relative to ~/src/user, to inspect Odoo.sh project contents. Use it to browse source directories when you need file locations.
List files and directories in a path
| Name | Required | Description | Default |
|---|---|---|---|
| dirPath | No | Directory path relative to ~/src/user (default: .) |
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 full burden. It does not mention whether the listing is recursive, what format the output takes, whether hidden files are included, or any permission requirements.
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, efficient sentence that front-loads the action and resource. No redundant or filler content.
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 listing tool with no output schema and no annotations, the description is minimal but functional. It omits return format, recursion behavior, and any ordering, which an agent would need to infer from the tool name alone.
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%, and the single parameter dirPath is fully documented in the schema including its default. The description adds no new parameter details but the schema already does the job; baseline for 1 param with full coverage is high.
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?
States a clear verb (List) and resource (files and directories) with scope limited to a path. It does not differentiate itself from sibling tools like read_file or get_logs, but the purpose is unmistakable.
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?
No indication of when to use this tool versus alternatives. With siblings like read_file and get_logs that could overlap in exploring the filesystem, explicit guidance is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.