Skip to main content
Glama
aadilakbar

MCP Odoo Bridge Server

by aadilakbar

search_records

Search Odoo database records by specifying model, filters, and fields to retrieve specific data for analysis or processing.

Instructions

Search for records in an Odoo model.

Args:
    model: The Odoo model name (e.g., 'res.partner', 'sale.order')
    domain: Search filter as Odoo domain list (e.g., [['is_company', '=', True]])
            Common operators: =, !=, >, <, >=, <=, like, ilike, in, not in
    fields: List of fields to return (empty = smart defaults)
    limit: Maximum records to return (default 80)
    offset: Number of records to skip (for pagination)
    order: Sort order (e.g., 'name asc, id desc')

Returns:
    JSON list of matching records

Examples:
    - Find all companies: model='res.partner', domain=[['is_company', '=', True]]
    - Find orders from this month: model='sale.order', domain=[['date_order', '>=', '2024-01-01']]
    - Find unpaid invoices: model='account.move', domain=[['payment_state', '!=', 'paid']]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
domainNo
fieldsNo
limitNo
offsetNo
orderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the search functionality and return format ('JSON list of matching records'), but doesn't mention important behavioral aspects like authentication requirements, rate limits, error handling, or whether this is a read-only operation (though 'search' implies it likely is). The examples help but don't fully compensate for missing behavioral context.

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?

The description is well-structured with clear sections (Args, Returns, Examples) and every sentence adds value. It's appropriately sized for a 6-parameter tool with complex domain syntax. The information is front-loaded with the core purpose first, followed by detailed parameter explanations and practical examples.

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 the tool's complexity (6 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description is quite complete. It thoroughly documents all parameters and provides helpful examples. The main gap is the lack of behavioral context and usage guidelines compared to sibling tools. The output schema handles return values, so the description doesn't need to explain those.

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?

Schema description coverage is 0%, so the description must fully document parameters. It provides excellent parameter semantics: each of the 6 parameters is clearly explained with examples, default values, and format expectations. The domain parameter explanation includes common operators, and the fields parameter clarifies that empty means 'smart defaults'. This goes well beyond what the bare schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 an Odoo model' which is a specific verb+resource combination. It doesn't explicitly differentiate from siblings like 'search_and_read_one' or 'get_record', but the purpose is unambiguous. The title is null, so the description carries the full burden of explaining the tool's function.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'search_and_read_one', 'get_record', or 'count_records'. It explains what the tool does but offers no context about appropriate use cases, prerequisites, or comparisons with sibling tools. The examples show how to use it but not when to choose it over other options.

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/aadilakbar/ad-mcp-bridge-server'

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