Skip to main content
Glama
The-TechX

odoo-mcp

by The-TechX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

odoo_create

Create a new record in any Odoo model by specifying the model name and field values, with access controlled by the configured Odoo user's permissions.

Instructions

Create a record in an Odoo model using the configured Odoo user permissions.

Input Schema

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

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 / 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

A3.5/5.0
Behavior3/5

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

The description adds the useful context that creation happens 'using the configured Odoo user permissions,' which signals an authorization dependency. However, it does not disclose other behavioral traits such as immediate persistence, possible side effects, or return behavior. Annotations already indicate non-read-only and non-idempotent, so the description contributes only modestly.

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 clear, front-loaded sentence with no filler. Every word contributes either to the core action or to the permission context.

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?

With no output schema, the description should explain the return value or result of the create operation, but it does not. It also omits error cases, required fields, and the relationship to the update/write operation. A mutation tool with minimal annotations needs more operational context.

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 coverage is only 50% since only 'model' has a description; 'values' has none. The description does not compensate by explaining that 'values' should be a mapping of Odoo field names to field values for the new record, leaving the agent to infer the key parameter's meaning.

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 specific verb and resource: 'Create a record in an Odoo model.' This clearly communicates the tool's core operation and distinguishes it from sibling tools like odoo_write (update), odoo_search_read, and odoo_unlink.

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 verb 'create' implies the tool is for adding new records rather than updating, reading, or deleting them, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives. Usage is inferred rather than stated.

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