Skip to main content
Glama
The-TechX

odoo-mcp

by The-TechX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

odoo_search_read

Read-onlyIdempotent

Search and read records from any Odoo model using filters, fields, and ordering, while respecting the configured API user's permissions.

Instructions

Search and read records from any Odoo model using the permissions of the configured Odoo API user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
modelYesTechnical Odoo model name, for example res.partner
orderNo
domainNoOdoo search domain
fieldsNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / $defs
      Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain / items / $ref
      Added value: +"#/$defs/__schema0"
    • removedInput schema / properties / domain / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  },
-  {
-    "items": {
-      "$ref": "#/properties/domain/items"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "$ref": "#/properties/domain/items"
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already convey readOnly, idempotent, and non-destructive behavior. The description adds useful context about results being scoped by the configured API user's permissions, but it does not disclose pagination behavior, return shape, or error/access boundary behavior.

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 front-loaded sentence with no filler. Every clause carries meaning: search, read, any Odoo model, and permission scoping.

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?

For a tool with six parameters, no output schema, and low schema coverage, this description is too sparse. It omits crucial operational details such as domain format, field list behavior, pagination through limit/offset, ordering, and what the returned records look like.

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?

With only 33% schema description coverage, the description needed to compensate for limit, order, fields, and offset semantics, but it does not mention any of them. It only reinforces the model parameter and the general search/read purpose, leaving most parameters under-explained.

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 ('Search and read') and a clear resource ('records from any Odoo model'). It naturally differentiates from sibling tools: create/write/unlink are mutations, and fields_get targets field metadata rather than records.

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

Usage Guidelines4/5

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

The read-only phrasing provides clear context for when to use this tool instead of the mutation siblings. However, it does not explicitly contrast with odoo_fields_get or state exclusion conditions, so it stops short of a 5.

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

Deploy Server

Other Tools