Skip to main content
Glama
bemade

odoo-mcp

by bemade

search_records

Read-only

Retrieve records from any Odoo model with domain filters, field selection, pagination, and sorting.

Instructions

Search for records in any Odoo model.

Args:
    model: The Odoo model name (e.g. "res.partner", "sale.order").
    domain: Odoo domain filter (e.g. [["is_company", "=", true]]).
        Defaults to [] (all records).
    fields: List of field names to return. Defaults to all fields.
    limit: Maximum number of records to return. Defaults to 80.
    offset: Number of records to skip (for pagination).
    order: Sort order (e.g. "name asc, id desc").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
domainNo
fieldsNo
limitNo
offsetNo
orderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate readOnlyHint=true. The description does not contradict and adds details about default values (limit=80, offset=0) and parameter behavior, which supplements the annotation.

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 concise with a clear first sentence and organized Args section. It could be slightly more front-loaded but is well-structured without extraneous content.

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?

All 6 parameters are explained, defaults are given, and examples provided. The return value is not described, but output schema exists, so completeness is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description explains each parameter's meaning, including model examples and domain format, adding significant value beyond the 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 clearly states 'Search for records in any Odoo model', using a specific verb and resource. This distinguishes it from sibling tools like create_record, delete_records, and read_record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly provide guidance on when to use this tool versus alternatives. While it explains parameters, it lacks when-not or alternative tool recommendations.

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

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