ERP/CRM via Odoo's external JSON-RPC API. Stateless multi-credential SaaS connector for querying Odoo instances.
Five tools with complete input schemas and descriptions. Naming follows verb_noun pattern (search_, list_, query_). Descriptions are clear and actionable (avg 180 chars, within baseline 194). All parameters have type definitions and descriptions. However, output schemas are NOT documented, LLMs cannot predict return structure. No error handling guidance. Credentials exposed as parameters (critical security issue). No pagination metadata (offset/limit accepted but no total_count or next_cursor returned). Generic parameter descriptions lack format constraints (e.g., 'domain' accepts arbitrary arrays without validation hints).
List Odoo CRM leads & opportunities (crm.lead). Returns name, contact, email_from, expected_revenue, probability, stage_id, and type (lead/opportunity). Use for "open opportunities" or "sales pipeline".
List Odoo customer invoices (account.move where move_type=out_invoice). Returns name, partner_id, amount_total, amount_residual, state (draft/posted/cancel), payment_state, and invoice_date. Use for "unpaid invoices" or "recent customer invoices".
List Odoo sales orders / quotations (sale.order). Returns name, customer (partner_id), amount_total, state (draft/sent/sale/done/cancel), and date_order. Optionally filter by state. Use for "recent sales orders" or "open quotations".
Power-user generic query: run search_read on ANY Odoo model. Provide model (e.g. "product.template"), domain (Odoo list-of-triples, e.g. [["list_price",">",100]]), fields, and limit. Use when no specific tool above fits.
Search Odoo contacts & companies (res.partner) by name, email, or company flag. Returns id, name, email, phone, and company/customer flags. Use for "find the contact/customer named X" or "list companies".
Credentials (_apiKey, url, db, username) exposed as tool parameters. Secrets in parameters are logged in traces and prompt history, creating compliance and security risks. Must use server-side secret injection via environment variables or vault.
Output schemas not documented. Tool descriptions state what fields are returned (e.g., 'Returns id, name, email, phone...') but no formal schema definition. LLMs cannot predict structure for downstream tool chaining or field extraction.
No error handling guidance. Code throws generic errors ('Odoo: authentication failed', 'Odoo: {detail}') without recovery hints. LLMs cannot determine if errors are retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
odoo_query_model 'domain' parameter accepts arbitrary arrays without validation hints. Description mentions 'list-of-triples' syntax but does not specify format constraints, valid operators, or field names. LLMs will hallucinate invalid domains.
Pagination not fully specified. Tools accept 'limit' but do not document total_count, next_cursor, or offset behavior in return structure. Large result sets risk context window exhaustion without clear pagination guidance.