Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

create_lead

Create a new CRM lead in Odoo with a preview-first flow: review exactly what will be written, then confirm to save it after user approval.

Instructions

Create a new CRM lead in Odoo, in two steps.

1. Call with confirm=false (the default): nothing is written; you get a preview
   of exactly what would be created. Show it to the user.
2. If the user approves, call again with the same arguments and confirm=true.

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": {
      "name": "<name>"
    },
    "name": "create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort title of the lead, e.g. 'Office chairs for Acme'.
emailNoContact email address.
confirmNofalse (default): only return a preview, nothing is written. true: actually create the lead. Only use true after the user has seen and approved the preview.
partner_nameNoCustomer company name.
expected_revenueNoExpected revenue in the company currency.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the critical fact that the default confirm=false performs no writes and returns a preview, which the agent could not know from annotations. It does not address duplicate handling if confirm=true is called repeatedly, despite idempotentHint=false, which is the main remaining behavioral gap.

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?

Front-loaded with the action, then a compact two-step protocol with no filler. Every sentence maps to a decision the agent must make about the confirm flag.

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?

Return values are covered by the output schema and the safety profile by annotations, so the description's job is the confirm protocol, which it handles fully. Minor gaps remain around repeated confirmed calls creating duplicates and what a failed write looks like.

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

Parameters3/5

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

Schema coverage is 100% and the confirm parameter's own description already explains preview versus actual creation, so the prose largely restates structured data. The two-step framing reinforces parameter meaning but adds no new syntax or constraints beyond the schema.

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 first line states a specific verb and resource ('Create a new CRM lead in Odoo') and the numbered steps make clear this is a write operation, which separates it from the read-oriented siblings like list_leads and get_sales_orders. It never names an alternative explicitly, so it falls short of full sibling differentiation.

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

Usage Guidelines5/5

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

The description prescribes exact usage: call first with confirm=false, show the preview to the user, then re-call with confirm=true only after approval. It states both the when (preview first) and the condition for the dangerous path (user approval), leaving nothing to inference.

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