Skip to main content
Glama

odoo_translate_context_aware

Translate Odoo records with domain-specific context, auto-detecting field types (plain text or HTML/XML) and preserving inline tags for natural, fluent outputs. Uses Claude AI to avoid literal translations.

Instructions

Translate Odoo records using Claude with rich domain context for natural, fluent results (not literal). AUTO-DETECTS field kind and handles both: (1) simple char/text fields (e.g. ir.ui.menu.name, account.account.name) → batch translate via update_field_translations; (2) HTML/XML fields (e.g. ir.ui.view.arch_db, website.page, product.template.website_description) → extracts canonical terms via get_field_translations, translates each term preserving inline HTML tags (, , ...), writes back in terms mode. Context to LLM: Odoo model, parent chain for menus, existing translations, user-supplied domain hint, field kind (simple/html/xml). Requires Odoo 16+. Requires ANTHROPIC_API_KEY env var (per-tenant override: ANTHROPIC_API_KEY_). Recommended models: 'claude-haiku-4-5' (menu labels, fast), 'claude-sonnet-4-6' (balanced, website pages), 'claude-opus-4-7' (complex legal/accounting terminology). ALWAYS use dry_run=true first to review proposals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionNodefault
modelYesOdoo model (e.g. 'ir.ui.menu', 'account.account', 'product.template')
idsYesRecord IDs to translate
field_namesNoTranslatable fields (default: ['name'])
target_langYesTarget language code (e.g. 'bg_BG', 'de_DE')
source_langNoSource language (usually 'en_US')en_US
context_hintNoFree-form domain hint ('accounting terms', 'manufacturing', 'Bulgarian NRA terminology', etc.)
claude_modelNoClaude model IDclaude-haiku-4-5
max_tokensNo
dry_runNoIf true, only preview (no writes).
Behavior3/5

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

No annotations provided, so description carries full burden. Explains auto-detection, translation strategies, context sent to LLM, requirements (Odoo 16+, API key), and recommended models. Missing details on error handling, permissions, or side effects.

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?

Efficiently packed with essential information in a structured, front-loaded format. Every sentence adds value without redundancy. The section on field kinds and model recommendations is well-organized.

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?

For a complex tool with 10 parameters and no output schema, the description is thorough. It covers the dual-mode behavior, context provisioning, and prerequisites. Missing explicit statement about return format or error scenarios, but overall sufficient.

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 80%, but description adds value by explaining the field kind auto-detection and the two processing modes. Provides context on how parameters like context_hint influence translation, which goes beyond schema descriptions.

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?

Specifically describes translation of Odoo records with rich domain context, auto-detects field kind, and distinguishes two modes (simple vs HTML/XML). Clearly differentiates from sibling tools like odoo_translate_field and odoo_translate_html.

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?

Provides clear guidelines: use for context-aware translation, recommends models based on complexity, advises dry_run first. Lacks explicit exclusions or direct comparison with siblings, but the context hints and recommendations are helpful.

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