odoo-mcp

Overview Schema Source Related Servers Discussions Admin

odoo_models

Lists Odoo database models such as res.partner and sale.order, enabling discovery of available entities for data operations.

Instructions

Lister les modèles disponibles (res.partner, sale.order, ...).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "odoo_models"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`name_contains`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.9.0Aug 11, 2026

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must convey behavioral traits. It only says 'Lister les modèles disponibles,' with no mention of read-only status, side effects, pagination, or potential performance implications. This leaves the agent without safety or behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the key information and includes no filler. It is efficiently structured for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the tool appears simple and has an output schema, the description omits parameter semantics and usage context. It covers only the core purpose, leaving the agent to infer how to use limit and name_contains and when to choose this tool over siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema includes two optional parameters (limit, name_contains) with defaults but no descriptions, and the description does not mention them at all. With 0% schema description coverage, the description fails to explain how these parameters affect results, though the field names are somewhat self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Lister') and resource ('les modèles disponibles') with concrete examples (res.partner, sale.order), making the tool's purpose unambiguous. It differentiates itself from siblings like odoo_fields (which would list fields) and odoo_search (search records).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to discover available model names, but it provides no explicit guidance on when to use it versus sibling tools such as odoo_fields or odoo_search. There is no mention of prerequisites or whether it should precede other Odoo operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.