Skip to main content
Glama

odoo_translate_field

Write translations for simple Odoo fields with translate=True. Supports multiple languages, clearing translations, and dry-run validation.

Instructions

Write translations for a simple translate=True field (Char/Text/Selection). Use for: blog.post.name/subtitle/teaser, product.template.name, res.partner.name, account.account.tag.name — any short/plain field. Format: translations = {lang_code: value, ...}. Pass value=null/'' to remove a language's translation (falls back to source_lang). Errors if field.translate is not True (use odoo_translate_html for HTML). Auto-detects Odoo version: v16+ uses update_field_translations() native API, older falls back to ir.translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNodefault
modelYes
res_idYes
field_nameYes
translationsYesMap of language code to new value: {'en_US': 'Name', 'bg_BG': 'Име', 'de_DE': 'Name'}. Supports null/empty to clear.
source_langNoSource language for fallback (default 'en_US')en_US
dry_runNoIf true, only validates and reports what would change without writing
mark_identical_as_translatedNoWhen True (default), a value that equals the source gets a U+200B (zero-width-space) prefix so Odoo keeps it as an explicit 'translated, kept identical' entry (avoids the 'untranslated' flag in the website editor).
Behavior4/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 discloses write operation, version auto-detection, fallback handling, dry_run mode, and mark_identical_as_translated behavior. Slightly lacks permissions or side-effect details.

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?

Description is concise with multiple sentences each adding information; front-loaded with purpose and examples. Could be more structured but efficient for its density.

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 8 parameters and no output schema, the description covers key aspects: usage, error, version, dry_run, and mark_identical. Missing return format and partial failure behavior, but sufficient for an action tool.

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 50%, and the description adds value by explaining the translations format and null handling, but does not explain 'connection', 'model', 'res_id', or 'field_name' beyond implicit context from examples.

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 tool writes translations for simple translate=True fields, lists example fields like blog.post.name and product.template.name, and distinguishes from odoo_translate_html by noting errors for non-translate fields.

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?

Explicitly tells when to use (simple translate=True fields) and when not (use odoo_translate_html for HTML), includes examples of valid fields, and explains how to remove translations with null/''.

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/rosenvladimirov/odoo-claude-mcp'

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