MCP Odoo Bridge Server

create_record

Add new records to Odoo by specifying the model and field values. Use this tool to create customers, products, or other data entries in your Odoo database.

Instructions

Create a new record in Odoo.

Args:
    model: The Odoo model name
    values: Dictionary of field values for the new record

Returns:
    Success message with the new record ID

Example:
    Create customer: model='res.partner', values={'name': 'New Customer', 'email': 'new@example.com'}

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": "create_record"
  }
}

Input Schema

Name	Required	Description	Default
`model`	Yes
`values`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the creation behavior and return format (success message with ID), but doesn't mention potential side effects, authentication requirements, error conditions, or rate limits. The description is adequate but lacks comprehensive behavioral context for a mutation tool.

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 efficiently structured with clear sections (Args, Returns, Example) and zero wasted text. Every sentence adds value: the purpose statement, parameter explanations, return specification, and concrete example all serve distinct functions.

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

Completeness4/5

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

Given this is a mutation tool with no annotations but with output schema (implied by 'Returns' statement), the description provides good coverage: purpose, parameters, return values, and example. It could benefit from mentioning prerequisites or error handling, but the example compensates for some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates well by explaining both parameters: 'model' as 'The Odoo model name' and 'values' as 'Dictionary of field values for the new record'. The example provides concrete syntax and format guidance beyond what the bare schema offers.

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 specific action ('Create a new record') and resource ('in Odoo'), distinguishing it from sibling tools like update_record, delete_record, or get_record. It provides a concrete example that reinforces the purpose.

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 description implies usage context through the example (creating a customer), but doesn't explicitly state when to use this tool versus alternatives like update_record for existing records or search_records for retrieval. It provides clear prerequisites (model and values) but lacks explicit exclusion guidance.

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

Deploy Server