Skip to main content
Glama
Sign In
Odoo Claude MCP

Odoo Claude MCP

by rosenvladimirov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

odoo_create

Create one or more Odoo records by specifying the model and field values. Supports batch creation with a list of dictionaries.

Instructions

Create one or more records. Returns list of new IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>",
      "values": "<values>"
    },
    "name": "odoo_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
valuesYesField values dict, or list of dicts for batch create
connectionNodefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions returning IDs but does not disclose behavioral traits such as whether the operation is destructive, authentication requirements, error handling, or rate limits. 'Create' implies mutation, but lacks further context.

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

Conciseness4/5

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

The description is highly concise with one sentence. It efficiently conveys the core function and return value. However, it could benefit from slightly more detail without becoming verbose.

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?

Given no output schema, the description does explain return values (list of IDs), but it omits key contextual information such as error handling, connection usage, and model constraints. The tool is simple but incomplete for an agent to use confidently.

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 33% (only 'values' has a description). The tool description adds no additional meaning for 'connection' or 'model' parameters. For a 3-parameter tool with low schema coverage, the description should compensate, but it does not.

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 clearly states the verb 'Create' and the resource 'records', and specifies it can create one or more records. It also indicates the return value (list of new IDs). This distinguishes it from sibling tools like odoo_read, odoo_write, etc. which have different actions.

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 for creating records, but it does not provide explicit guidance on when to use it versus alternatives (e.g., when to use odoo_execute instead). No context on prerequisites or when not to use is given.

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