Skip to main content
Glama
erpipe-org

Odoo MCP Server

by erpipe-org
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

diagnose_odoo_call

Read-onlyIdempotent

Diagnose Odoo model method calls before execution, identifying potential errors and compatibility issues using optional parameters for transport, version, and observed errors.

Instructions

Diagnose an Odoo model call without executing it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoOptional positional call arguments.
modelYesTechnical Odoo model name to diagnose.
kwargsNoOptional keyword call arguments.
methodYesOdoo model method name to diagnose.
metadataNoOptional model or method metadata used by the diagnosis.
transportNoTransport to assess, such as 'auto', 'xmlrpc', or 'json2'.auto
include_debugNoWhether to include additional diagnostic details.
observed_errorNoOptional error text or structured error to classify.
target_versionNoOptional target Odoo version for compatibility checks.
use_live_metadataNoWhether to request live metadata; this preview tool does not fetch it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed10 schema fields changedv1.2.1
    • addedInput schema / properties / args / description
      Added value: +"Optional positional call arguments."
    • addedInput schema / properties / include_debug / description
      Added value: +"Whether to include additional diagnostic details."
    • addedInput schema / properties / kwargs / description
      Added value: +"Optional keyword call arguments."
    • addedInput schema / properties / metadata / description
      Added value: +"Optional model or method metadata used by the diagnosis."
    • addedInput schema / properties / method / description
      Added value: +"Odoo model method name to diagnose."
    • addedInput schema / properties / model / description
      Added value: +"Technical Odoo model name to diagnose."
    • addedInput schema / properties / observed_error / description
      Added value: +"Optional error text or structured error to classify."
    • addedInput schema / properties / target_version / description
      Added value: +"Optional target Odoo version for compatibility checks."
    • addedInput schema / properties / transport / description
      Added value: +"Transport to assess, such as 'auto', 'xmlrpc', or 'json2'."
    • addedInput schema / properties / use_live_metadata / description
      Added value: +"Whether to request live metadata; this preview tool does not fetch it."
  2. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds 'without executing it', reinforcing safety but providing no additional behavioral details beyond what annotations convey.

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 description is a single, concise sentence that immediately conveys the tool's purpose. No unnecessary words or 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?

Given the tool has 10 parameters and an output schema, the description is brief but sufficient to understand the core functionality. However, it could briefly mention that the tool analyzes potential issues without side effects, which would improve completeness.

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 100%, so baseline is 3. The tool description adds no extra meaning beyond the parameter descriptions in the schema (e.g., it doesn't explain how 'metadata' or 'transport' affect diagnosis).

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 explicitly states 'Diagnose an Odoo model call without executing it', clearly defining the action (diagnose), the resource (Odoo model call), and the key constraint (no execution). This distinguishes it from sibling tools like 'execute_method' which performs actual execution.

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?

The description implies usage for diagnosis, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'execute_method', 'preview_write'). There is no mention of use cases or exclusions.

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