Skip to main content
Glama
solutionsunity

OdooSurface MCP

translation_update

Write translations for translatable fields in Odoo records, supporting single or batch updates with per-field and per-language content.

Instructions

💡 Before multi-step work, check find_skill / list_workflows for canonical recipes. Write translations for translatable field(s). Two forms: (1) Single/same-map — pass record_id (a number or an array of ids), field_name and translations; the same translations map is applied to every id. (2) Batch — pass updates: [{record_id, field_name, translations}, ...] to write different content per record and per field in one call (e.g. name + html_content for many records). For char fields (translate=True): translations = {"fr_FR": "Bonjour", "ar_001": "مرحبا"}. For html / arch_db fields (callable translate): translations = {"fr_FR": {"English source term": "French translation"}}. The target language must be installed in Odoo (Settings → Languages). Single id (number) form returns {success: true}; id-array and batch forms return {results: [{record_id, field_name, success: true} | {record_id, field_name, error}]}. Returns the above or {error}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
updatesNo
record_idNo
field_nameNo
translationsNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the structure of translations for char vs html fields, the requirement that the target language be installed, and the return formats for different input forms. It does not mention permissions or side effects but covers essential behavioral traits.

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 well-organized with clear separation of forms and bullet points for examples. It is front-loaded with the purpose and the initial note about find_skill/list_workflows. While somewhat lengthy, every sentence is informative.

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 no output schema, the description adequately explains return values for different input forms. It covers error cases with {error} and mentions language installation. Minor gaps exist, such as not clarifying partial batch failures or the error for missing language, but overall it is fairly complete.

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 coverage is 0%, but the description explains all parameters in context, including examples for translations objects and the difference between single and batch forms. The model parameter is mentioned as required but not elaborated; overall, it adds significant meaning beyond the raw schema.

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 explicitly states 'Write translations for translatable field(s)' and distinguishes two forms: single/same-map and batch. It specifies the resource (translatable fields on a model) and clearly differentiates from sibling tools like translation_get (reading) and translation_audit (auditing).

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?

It provides guidance on when to use each form (single vs batch) and suggests checking find_skill/list_workflows before multi-step work. However, it does not explicitly exclude alternatives or explain when not to use this tool compared to other update tools like create or update.

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/solutionsunity/odoo-surface-mcp'

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