odoo_sh_logsTail Odoo logs from the build container, supporting optional grep filtering and line count selection.
Tail Odoo logs (odoo.log, install.log or pip.log) from the configured Odoo.sh build container via SSH. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| grep | No | Optional fixed-string filter (case-insensitive), e.g. 'ERROR' | |
| lines | No | ||
| log_type | No | odoo |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false; description reinforces this with 'Read-only' and adds context about SSH and specific log files. It does not describe return format, whether the tail is continuous, or any operational caveats, but no contradiction exists.
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 short sentences with no redundant phrasing. The core action, target, and safety are front-loaded.
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?
Provides purpose and safety but omits parameter semantics and output expectations. Without an output schema or usage guidance, an agent cannot fully infer what the tool will return or when to prefer it.
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?
Only grep has a schema description; lines and log_type lack descriptions, and schema coverage is 33%. The description lists log file names but does not explain the parameters, defaults, or how log_type maps to the enumerated 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?
Clearly states the action (Tail/read), resource (Odoo logs), and scope (odoo.log, install.log, pip.log) from the configured build container via SSH. The read-only nature is explicit and it is distinguishable from sibling tools like system_info or search_read.
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 guidance on when to use this tool instead of siblings such as odoo_sh_status or odoo_sh_system_info. It does not mention prerequisites, exclusions, or typical scenarios, leaving selection entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.