Skip to main content
Glama

Odoo

by io.github.pipeworx-io

Odoo Query Model

odoo_query_model
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbYesOdoo database name.
urlYesOdoo instance base URL, e.g. https://mycompany.odoo.com (trailing slash optional). Works for Odoo Online and self-hosted.
limitNoMax records (default 20).
modelYesOdoo model name, e.g. "product.template", "stock.picking", "hr.employee".
orderNoSort spec, e.g. "create_date desc".
domainNoOdoo search domain — a list of triples [field, operator, value], e.g. [["active","=",true],["name","ilike","acme"]]. Empty array [] matches all.
fieldsNoField names to return, e.g. ["name","create_date"]. Omit to let Odoo return its default field set.
offsetNoNumber of records to skip (pagination).
_apiKeyYesOdoo API key (Settings → Account Security → API Keys) or account password.
usernameYesOdoo login email.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds context about domain syntax and that it's a 'power-user generic query,' but does not disclose additional behavioral traits like pagination, error handling, or performance implications beyond the annotations.

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?

Two sentences efficiently front-load the purpose and provide key usage instructions without extraneous detail. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite high complexity (10 parameters, generic tool) and no output schema, the description does not explain the return format, error handling, or behavior for edge cases. It leaves agents without a clear picture of what to expect from the 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 100% so baseline is 3. The description provides helpful examples and reinforces domain format, but does not add significant new semantic meaning beyond what the schema already provides.

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 runs search_read on ANY Odoo model, provides examples of model names and domain format, and explicitly distinguishes from sibling tools by advising to use it when no specific tool above fits.

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?

Explicit guidance to use when no specific tool fits, with examples showing typical usage. Lacks explicit instructions on when to avoid or alternative tools beyond siblings, but the fallback nature is well communicated.

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

All Odoo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Some tools have overlapping purposes (e.g., ask_pipeworx and ask_pipeworx_grounded; multiple Polymarket analysis tools) but descriptions help differentiate. Odoo-specific tools are distinct among themselves but muddled with many general-purpose tools.

Naming Consistency2/5

Naming is heavily inconsistent: Odoo tools follow 'odoo_list_*' pattern while others use varied structures like verb-first (forget, remember) or noun-first (entity_profile, recent_alerts). No unified verb_noun pattern across the set.

Tool Count3/5

At 32 tools, the server exceeds the typical well-scoped range (3–15) but is not excessively large. Many tools are generic and could be trimmed, making the set feel heavier than necessary.

Completeness2/5

Despite many tools, the server lacks essential CRUD operations for Odoo (e.g., create/update/delete leads) and the 'Odoo' name misrepresents the actual focus. Gaps in Odoo functionality and mixed domains create a sense of incompleteness.

Resources