Odoo MCP Server

list_models

Read-onlyIdempotent

Discover available Odoo models and filter by name to find relevant data structures for your ERP queries.

Instructions

List Odoo models with optional name filtering

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`instance`	No

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No	Reporting tool name.
`count`	No
`error`	No	Sanitized error message when success is false.
`result`	No
`success`	Yes	False when the call failed; see error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.1.0Jul 5, 2026

addedOutput schema / $defs

Added value: +{
+  "ModelSummary": {
+    "additionalProperties": true,
+    "description": "One model entry from list_models / schema_catalog.",
+    "properties": {
+      "model": {
+        "description": "Technical model name, e.g. res.partner.",
+        "title": "Model",
+        "type": "string"
+      },
+      "name": {
+        "default": "",
+        "description": "Human display name.",
+        "title": "Name",
+        "type": "string"
+      }
+    },
+    "required": [
+      "model"
+    ],
+    "title": "ModelSummary",
+    "type": "object"
+  }
+}

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Count"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sanitized error message when success is false.",
+  "title": "Error"
+}

removedOutput schema / properties / result / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / result / anyOf

Added value: +[
+  {
+    "items": {
+      "$ref": "#/$defs/ModelSummary"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / result / default
```
Added value: +null
```
removedOutput schema / properties / result / type
```
Removed value: -"object"
```

addedOutput schema / properties / success

Added value: +{
+  "description": "False when the call failed; see error.",
+  "title": "Success",
+  "type": "boolean"
+}

addedOutput schema / properties / tool

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Reporting tool name.",
+  "title": "Tool"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "success"
+]

changedOutput schema / title

Previous value: -"list_modelsOutput"New value: +"ListModelsResponse"

Changed1 schema field changedv1.0.0Jun 12, 2026

addedInput schema / properties / instance

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instance"
+}

First observedv0.2.0Apr 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds no behavioral traits beyond the filtering behavior implied by the query parameter, and does not mention latency, auth requirements, or pagination.

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?

A single, clear sentence with no wasted words. The core action and optional filter are front-loaded, making it easy to scan.

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

Completeness3/5

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

Given the tool's simplicity (3 optional params, output schema present), the description is adequate but minimal. It does not clarify what the output contains (e.g., model names only vs. full details) or how 'limit' and 'instance' affect results, leaving some ambiguity.

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?

Schema description coverage is 0%, so the description must explain all parameters. It only hints at 'query' for name filtering but provides no explanation for 'limit' or 'instance'. The output schema exists but is not described, so the agent cannot infer return structure from this description.

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 uses a specific verb 'List' and clearly identifies the resource 'Odoo models', with the optional name filtering hint. It distinguishes the tool from siblings like 'search_records' or 'get_model_fields' by focusing on listing models themselves.

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

Usage Guidelines2/5

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 alternatives such as 'search_records' or 'get_model_fields'. The description implies a use case (listing models with optional filtering) but does not specify exclusions or preferred contexts.

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