Skip to main content
Glama
Odoo Connect MCP

Odoo Connect MCP

by Tristan439

Read records by ID

read_records
Read-onlyIdempotent

Fetch specific Odoo records by model and record IDs, optionally choosing fields, so you can query exact data instead of scanning entire models.

Instructions

Reads specific records by their IDs.

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

Input Schema

NameRequiredDescriptionDefault
idsYes
modelYesTechnical model name, e.g. "sale.order", "res.partner", "crm.lead"
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing behavioral beyond that: it does not say what happens when an ID does not exist (error vs. skip), whether the 200-ID cap is enforced, or what a default field set contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, which is structurally clean. However, the brevity is closer to under-specification than genuine conciseness, since nothing about the parameters or ID-resolution behavior is captured.

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

Completeness2/5

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

There is no output schema, and the description does not describe the return shape (record objects keyed by model, field selection defaults). For a tool with three parameters, one-third schema coverage, and a hard 200-ID limit, the definition leaves too much for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — only "model" carries a description (with examples) in the schema. The description does not explain the "ids" list semantics (positive integers, 1–200 items, behavior for missing IDs) or what the optional "fields" array controls, leaving a third of the parameters undocumented in both places.

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 (reads) and resource (records) plus the access method (by their IDs), which lets an agent distinguish it from count_records or aggregate_records. It stops short of naming search_records, the closest alternative for query-based retrieval, so the contrast is only implied.

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?

"By their IDs" implicitly signals the condition for use (the agent already holds identifiers), but there is no explicit when-not guidance or reference to search_records for query-based lookup. The agent must infer the boundary from the sibling name alone.

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