Discover Odoo models available to a connection, helping you identify the right records and fields for search, read, or update operations.
Find Odoo models available to this connection.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| domain | No | ||
| connection_id | Yes |
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 burden. It says nothing about whether results are paginated, whether 'find' implies search semantics, what authentication or permissions are needed on the Odoo connection, or roughly what the response contains.
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 front-loaded sentence with no wasted words, but the brevity is under-specification rather than efficient compression — nothing actionable is conveyed beyond the title.
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 3-parameter tool with no annotations, no output schema, and 0% schema descriptions, the definition leaves too much undocumented. An agent would have to open the schema and guess at domain syntax and pagination behavior.
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 0% across 3 params. 'this connection' weakly implies connection_id, but limit (default 50) and especially domain, an Odoo-specific filter syntax with no schema description at all, receive no explanation in the description.
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 specific verb and resource: find Odoo models scoped to a connection. An agent can tell this apart from record-level siblings, though it doesn't explicitly distinguish itself from model_fields_get, which operates on a single model.
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 versus model_fields_get, record_search, or server_info_get. The natural workflow (list models, then fetch fields) is left entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.