odoo-safe-mcp

odoo_search

Read-onlyIdempotent

Search Odoo records and return selected fields using domains, pagination, and sorting for read-only reporting and data lookup.

Instructions

Search Odoo records and return their fields (search_read). Read-only.

Args: model: Technical model, e.g. 'res.partner', 'sale.order', 'account.move'. domain: Odoo domain, e.g. [["state", "=", "sale"], ["amount_total", ">", 1000]]. fields: Fields to return. Use odoo_describe_model to discover them; omit for all. limit: Max records (default 20, max 200). offset: Records to skip, for pagination. order: Sort, e.g. 'date_order desc'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>"
    },
    "name": "odoo_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`model`	Yes
`order`	No
`domain`	No
`fields`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Oct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description's 'Read-only' is consistent reinforcement. It adds real behavior detail beyond the annotations: the default limit of 20 and a hard maximum of 200 (the schema only shows the default), plus the fact that omitting fields returns all fields. Return format is left to the output schema, which exists.

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 purpose is stated in the first sentence before any arguments, and the Args block is a compact one-line-per-parameter list with no filler. Nothing repeats the schema verbatim and every line carries information.

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 six-parameter, open-domain search tool with no schema descriptions, this covers syntax for every parameter, defaults, and where to find field names; the output schema handles return values. The only shortfall is the absence of explicit routing guidance relative to odoo_read and odoo_count.

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 carry the full burden, and it does: model is illustrated with concrete technical names ('res.partner', 'sale.order'), domain is given a real Odoo domain literal, fields is tied to odoo_describe_model with omit-for-all semantics, limit states default and max, offset is framed as pagination, and order shows a sort string. Every one of the six parameters gains meaning not present in the schema.

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?

States a specific verb and resource ('Search Odoo records and return their fields') and even names the underlying RPC method (search_read), so the agent knows exactly what operation occurs. It doesn't explicitly contrast with siblings like odoo_read or odoo_count, which would have pushed this to a 5.

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?

It gives implicit guidance by pointing to odoo_describe_model for field discovery and showing a domain example, which is genuinely useful. But it never says when to prefer this over odoo_read (presumably ID-based retrieval) or odoo_count/odoo_aggregate, leaving the agent to infer the selection rules from the sibling names alone.

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

Deploy Server