Skip to main content
Glama
The-TechX

odoo-mcp

by The-TechX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

odoo_write

Idempotent

Update one or more Odoo records by providing the model, record IDs, and field values to modify, with access controlled by the configured Odoo user's permissions.

Instructions

Update one or more Odoo records using the configured Odoo user permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
modelYesTechnical Odoo model name, for example res.partner
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / ids / items / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / values / additionalProperties / $ref
      Added value: +"#/$defs/__schema0"
    • removedInput schema / properties / values / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  },
-  {
-    "items": {
-      "$ref": "#/properties/values/additionalProperties"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "$ref": "#/properties/values/additionalProperties"
-    },
-    "type": "object"
-  }
-]
    • addedInput schema / properties / values / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, idempotent operation. The description adds a small but useful behavioral note about running under the configured Odoo user permissions, but it does not disclose partial-failure behavior or outcomes when permissions are insufficient.

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 front-loaded sentence with no filler. The update action and permission context are the most important information and appear first.

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 write operation with an under-described values object, no output schema, and no return-value hints, the description is too thin. It omits important invocation context such as how ids map to records, what values accepts, and what result or failure behavior the agent should expect.

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?

Only the model parameter is documented in the schema, with schema description coverage at 33%. The tool description does not explain that values should be an Odoo field-value map or that ids must identify existing records, so it fails to compensate for the gaps around ids and values.

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

Purpose4/5

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

The description uses a specific verb ('Update') with a clear resource ('one or more Odoo records') and adds the scope of operating under configured permissions. It is clear but does not explicitly distinguish this from sibling tools like odoo_create or odoo_unlink, though the update semantics are inferable.

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?

There is no guidance on when to use this tool versus the sibling alternatives odoo_create, odoo_unlink, or odoo_search_read. The description only implies existing-record updates from the word 'Update' and does not state exclusions or prerequisites.

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