Skip to main content
Glama
erpipe-org

Odoo MCP Server

by erpipe-org
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

diagnose_access

Read-onlyIdempotent

Diagnose ACL and record-rule visibility for an Odoo model using optional domains, operations, and record IDs to pinpoint access denials and hidden records.

Instructions

Diagnose ACL and record-rule visibility for an Odoo model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum metadata rows to inspect; capped at 500.
modelYesTechnical Odoo model name to inspect.
domainNoOptional Odoo domain used for the visibility check.
instanceNoOptional configured Odoo instance name; uses the default if omitted.
operationNoAccess operation to diagnose, such as read or write.read
record_idsNoOptional record IDs to check directly.
include_rulesNoWhether to include matching record-rule metadata.
expected_countNoOptional expected visible record count for comparison.
observed_errorNoOptional error text or structured error to classify.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv1.2.1
    • addedInput schema / properties / domain / description
      Added value: +"Optional Odoo domain used for the visibility check."
    • addedInput schema / properties / expected_count / description
      Added value: +"Optional expected visible record count for comparison."
    • addedInput schema / properties / include_rules / description
      Added value: +"Whether to include matching record-rule metadata."
    • addedInput schema / properties / instance / description
      Added value: +"Optional configured Odoo instance name; uses the default if omitted."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum metadata rows to inspect; capped at 500."
    • addedInput schema / properties / model / description
      Added value: +"Technical Odoo model name to inspect."
    • addedInput schema / properties / observed_error / description
      Added value: +"Optional error text or structured error to classify."
    • addedInput schema / properties / operation / description
      Added value: +"Access operation to diagnose, such as read or write."
    • addedInput schema / properties / record_ids / description
      Added value: +"Optional record IDs to check directly."
  2. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / instance
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instance"
+}
    • addedInput schema / properties / observed_error
      Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Observed Error"
+}
  3. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveness; the description confirms the diagnostic nature but adds no further behavioral details (e.g., output volume, execution cost).

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 single-sentence description is concise, front-loaded with the verb and resource, and contains no redundant 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 9-parameter tool with full schema and an output schema, the brief description is mostly adequate, though it could briefly mention the nature of the diagnostic output (e.g., 'returns ACL analysis').

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 the description does not need to explain parameters; it adds no extra meaning beyond what the schema already provides, meeting the baseline.

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 clearly states the verb 'diagnose' and the resource 'ACL and record-rule visibility for an Odoo model', making the tool's specific purpose distinct from sibling diagnostic tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like diagnose_odoo_call or when to avoid it; the description lacks context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erpipe-org/mcp-odoo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server