Skip to main content
Glama
odoo-mcp

odoo-mcp

by affifariza04

search_records

Read-only

Query records from an allowed Odoo model using domain filters, selected fields, ordering, and row limits to retrieve sales, customer, stock, or invoice data safely.

Instructions

Generic read: Odoo search_read on an allowed model. Domain uses Odoo syntax, e.g. [["state","=","sale"],["amount_total",">",1000000]].

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": "search_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
modelYes
orderNo
domainNo
fieldsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the bar is lower. The description does add one piece of non-obvious behavior not in the annotations — that only "allowed" models are queryable — but it says nothing about what happens on a disallowed model, whether fields default to all columns, or how many records come back by default.

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?

Two sentences, front-loaded with the operation type and then the domain syntax, with the example doing real work rather than padding. The 1,000,000 threshold in the example is arbitrary but harmless as illustration.

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

Completeness3/5

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

An output schema exists, so return-value shape need not be described. However, for a generic query surface over arbitrary models, the definition omits the model allowlist, the default 20-record cap and pagination behavior, and how fields/order interact — gaps that matter for correct invocation on a 5-parameter 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 description coverage is 0%, so the description carries the burden, and it covers the hardest parameter well by showing an Odoo domain expression with operators and a numeric threshold. It contributes nothing about model (which models are "allowed"?), fields projection, order syntax, or limit semantics, so four of five parameters are left to name inference.

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 names a concrete operation and underlying mechanism: "Odoo search_read on an allowed model," so an agent knows this is a generic search-plus-read, not a domain-specific query. It is clear on its own terms but never explicitly contrasts itself with the domain-specific siblings (check_stock, overdue_invoices, etc.).

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?

"Generic read" implies this is the catch-all/fallback path when no specialized tool applies, but that is left to inference. There is no explicit when-to-use, when-not-to-use, or named alternative, so routing decisions against the sibling tools remain guesswork.

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