Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

Search records

search_records
Read-onlyIdempotent

Query Odoo model records by domain and return selected fields, total count, and pagination status.

Instructions

Searches records of a model with an Odoo domain and returns their fields. Returns total count and has_more for pagination.

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
modelYesTechnical model name, e.g. "sale.order", "res.partner", "crm.lead"
orderNoe.g. "date_order desc, id desc"
domainNoOdoo domain, e.g. [["state","=","sale"],["amount_total",">",1000]]. Empty = all records.
fieldsNoFields to return. Omit for a sensible default set.
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing that the response includes a total count and has_more for pagination, but it says nothing about default field selection, ordering behavior, or what happens when domain is omitted beyond the schema's note.

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, no filler, with the core action front-loaded and the return/pagination contract placed second where it belongs.

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?

With six parameters, no output schema, and only 67% schema coverage, the description should do more: it never describes the shape of the returned records array or the default field set. It covers the pagination return contract but not the overall response structure.

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 67%, and the schema itself documents model, domain, fields, and order with examples. The description only echoes 'with an Odoo domain' and 'returns their fields', adding no meaning beyond the schema and leaving limit/offset pagination semantics to 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?

The description names a specific verb and resource ('Searches records of a model') and adds the domain-based filtering mechanism. It is clear on what the tool does, but it does not distinguish itself from siblings like read_records or aggregate_records, which also touch the same records.

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?

Usage is only implied: the mention of an Odoo domain suggests filtered retrieval, but there is no explicit when-to-use guidance and no routing between this tool and read_records, count_records, or aggregate_records. The agent must infer that this is the 'filtered list' option.

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