MCP Odoo Bridge Server

delete_record

Remove a specific record from Odoo by specifying its model and ID. This action permanently deletes data and cannot be undone.

Instructions

Delete a record from Odoo.

Args:
    model: The Odoo model name
    record_id: The ID of the record to delete

Returns:
    Success message

⚠️ WARNING: This action is irreversible!

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>",
      "record_id": "<record_id>"
    },
    "name": "delete_record"
  }
}

Input Schema

Name	Required	Description	Default
`model`	Yes
`record_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 6, 2026

TDQS

B3.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 the full burden of behavioral disclosure. It states the action is irreversible (a key behavioral trait) and mentions a success message return, but lacks details on error handling, authentication needs, or rate limits. This is adequate but has clear gaps for a destructive operation.

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 appropriately sized and front-loaded with the core action, followed by structured sections for args and returns. The warning is placed effectively, but the 'Returns' section could be more concise (e.g., merging with the main text). Overall, it's efficient with minimal waste.

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

Completeness3/5

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

Given the tool's complexity (destructive operation with 2 parameters) and no annotations, the description is moderately complete: it covers purpose, parameters, returns, and a critical warning. However, with an output schema present, the return value explanation is redundant, and it lacks context on permissions or error cases, leaving room for improvement.

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 description coverage is 0%, so the description must compensate. It adds basic meaning for both parameters ('model' as Odoo model name, 'record_id' as ID to delete), which is helpful beyond the bare schema. However, it doesn't provide examples, constraints, or format details, keeping it at a baseline level.

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 clearly states the verb ('Delete') and resource ('a record from Odoo'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'update_record' or 'create_record' beyond the action name, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_record' or 'create_record', nor does it mention prerequisites such as permissions or dependencies. The warning about irreversibility hints at caution but doesn't specify usage contexts or exclusions.

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

Deploy Server