Query Odoo records by running a search_read on models like sale.order, res.partner, or product.product. Retrieve specific fields and apply filters to get the needed data.
Run a search_read against any Odoo model (e.g. sale.order, res.partner, product.product)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| model | Yes | ||
| domain | No | ||
| fields | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description must carry the full burden of behavioral disclosure. It only says 'search_read' which implies a read operation, but it does not mention side effects, permissions, pagination, error handling, or any operational traits. This is a significant gap for a generic data access tool.
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, concise sentence with no wasted words. It is front-loaded with the action and resource, making it easy to parse. However, it is so brief that it sacrifices essential detail, but for conciseness and structure alone it scores well.
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?
Given the tool's generic nature (any model) and four parameters with no schema descriptions, no output schema, and no annotations, the description is severely incomplete. It lacks guidance on domain syntax, field selection, limit behavior, return format, and edge cases. An agent would struggle to use this tool correctly based solely on the description.
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 input schema has zero parameter descriptions (coverage 0%), and the description does not explain any of the four parameters (model, domain, fields, limit). The examples mention model values but not the semantics of the other parameters, leaving the agent with no guidance on how to construct a valid domain or interpret the limit.
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 a specific action ('Run a search_read') against a specific resource (any Odoo model), with examples. It distinguishes from sibling tools by being generic while siblings are model-specific, though it doesn't explicitly name alternatives.
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 is provided on when to use this tool versus the siblings like odoo_get_stock_level or odoo_create_sale_order. The description only states what it does, not when it should be chosen over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.