Skip to main content
Glama
aadilakbar

MCP Odoo Bridge Server

by aadilakbar

update_record

Modify existing records in Odoo by specifying the model, record ID, and updated field values to maintain accurate data.

Instructions

Update an existing record in Odoo.

Args:
    model: The Odoo model name
    record_id: The ID of the record to update
    values: Dictionary of field values to update

Returns:
    Success message

Example:
    Update customer phone: model='res.partner', record_id=5, values={'phone': '123-456-7890'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
record_idYes
valuesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Update' implying mutation but doesn't disclose behavioral traits like required permissions, whether changes are reversible, error handling, or rate limits. The example adds minimal context but lacks comprehensive behavioral details needed 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 well-structured and front-loaded with the core purpose, followed by Args, Returns, and Example sections. Every sentence earns its place, with no redundant information, making it efficient and easy to parse.

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 complexity (mutation tool with 3 params, nested objects, no annotations) and an output schema (implied by 'Returns'), the description is moderately complete. It covers parameters and includes an example but lacks behavioral context and usage guidelines, leaving gaps for safe and effective tool invocation.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters ('model', 'record_id', 'values') in the Args section and reinforces with an example, adding meaningful context beyond the bare schema. However, it doesn't detail constraints like valid model names or value formats.

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 action ('Update') and target ('an existing record in Odoo'), providing specific verb+resource. However, it doesn't explicitly differentiate from siblings like 'create_record' or 'delete_record' beyond the 'existing' qualifier, which is implied but not contrasted directly.

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 'create_record' or 'delete_record'. It mentions 'existing record' but doesn't specify prerequisites, exclusions, or contextual triggers for choosing this over other mutation tools in the sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadilakbar/ad-mcp-bridge-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server