Skip to main content
Glama
Sign In
odoo-mcp-server

odoo-mcp-server

by Calderkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Read records

odoo_read
Read-onlyIdempotent

Read specific Odoo records by ID and return selected fields as model, count, and records; use when IDs are known, with missing IDs reported separately.

Instructions

Read specific records of one model by id, at most 100 per call, and return their fields as {model, count, records}. Use it when you already have ids (from odoo_search, a relation field or the user); to find records by criteria use odoo_search, for a number only odoo_count. Ids that do not exist are listed in missing_ids instead of failing; if one of the records is outside your access rights, the call fails with an access error. Values are formatted as in odoo_search.

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>",
      "ids": "<ids>"
    },
    "name": "odoo_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRecord ids to read, e.g. [7, 12]. At most 100.
modelYesTechnical model name from odoo_list_models, e.g. 'res.partner' or 'sale.order'.
fieldsNoField names to return, from odoo_describe_model. Omit for a default selection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • changedInput schema / properties / fields / description
      Previous value: -"Field names to return. Leave empty for a sensible default set."New value: +"Field names to return, from odoo_describe_model. Omit for a default selection."
    • addedInput schema / properties / ids / description
      Added value: +"Record ids to read, e.g. [7, 12]. At most 100."
    • changedInput schema / properties / model / description
      Previous value: -"Technical model name, e.g. 'res.partner'."New value: +"Technical model name from odoo_list_models, e.g. 'res.partner' or 'sale.order'."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them by disclosing failure semantics: nonexistent ids land in missing_ids rather than erroring, while a record outside the caller's access rights fails the whole call. That is exactly the kind of non-obvious runtime behavior an agent needs before invoking the tool.

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?

Return shape and constraint are front-loaded, and each clause carries information (scope, cap, alternatives, error behavior, formatting). It is a dense two-sentence chain, slightly run-on, but nothing is wasted.

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

Completeness5/5

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

With no output schema, the description still supplies the response shape and a formatting reference ('as in odoo_search'), plus partial-failure and access-error behavior. Nothing essential for a correct call is missing.

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 100%, so model, ids, and fields are already documented in the schema, and the description mainly restates the 100-id cap already enforced by maxItems. The only real addition is the provenance hint for ids (odoo_search, relation fields, the user), so the baseline of 3 applies.

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 states a specific verb and resource ('Read specific records of one model by id'), names the key constraint (at most 100 per call), and gives the exact return shape {model, count, records}. An agent can distinguish this from odoo_search or odoo_count without opening any schema.

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

Usage Guidelines5/5

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

It explicitly says when to use it ('when you already have ids (from odoo_search, a relation field or the user)') and names the alternatives with the conditions that select them ('to find records by criteria use odoo_search, for a number only odoo_count'). Both the use case and the exclusions are stated outright.

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

Deploy Server

Other Tools