Skip to main content
Glama
erpipe-org

Odoo MCP Server

by erpipe-org
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

get_odoo_profile

Read-onlyIdempotent

Retrieve a bounded profile of the connected Odoo environment, including configured instance and installed module metadata, to quickly assess its setup.

Instructions

Read a bounded profile of the connected Odoo environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoOptional configured Odoo instance name; uses the default if omitted.
module_limitNoMaximum installed modules to include; capped at 500.
include_modulesNoWhether to include installed-module metadata.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoReporting tool name.
errorNoSanitized error message when success is false.
profileNoServer, user-context, transport, and module metadata.
successYesFalse when the call failed; see error.
metadata_usedNo

Schema Changelog

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

  1. Changed3 schema fields changedv1.2.1
    • addedInput schema / properties / include_modules / description
      Added value: +"Whether to include installed-module metadata."
    • addedInput schema / properties / instance / description
      Added value: +"Optional configured Odoo instance name; uses the default if omitted."
    • addedInput schema / properties / module_limit / description
      Added value: +"Maximum installed modules to include; capped at 500."
  2. Changed9 schema fields changedv1.1.0
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / properties / error
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Sanitized error message when success is false.",
+  "title": "Error"
+}
    • addedOutput schema / properties / metadata_used
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Metadata Used"
+}
    • addedOutput schema / properties / profile
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Server, user-context, transport, and module metadata.",
+  "title": "Profile"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Result",
-  "type": "object"
-}
    • addedOutput schema / properties / success
      Added value: +{
+  "description": "False when the call failed; see error.",
+  "title": "Success",
+  "type": "boolean"
+}
    • addedOutput schema / properties / tool
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Reporting tool name.",
+  "title": "Tool"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "success"
+]
    • changedOutput schema / title
      Previous value: -"get_odoo_profileOutput"New value: +"GetOdooProfileResponse"
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / instance
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instance"
+}
  4. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds minimal behavioral context beyond 'bounded', leaving the precise scope unclear. No contradiction with annotations.

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?

A single, concise sentence front-loads the core action. No extraneous text, and every word is meaningful.

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?

While the output schema exists (reducing need to describe returns), the term 'bounded profile' is vague. The description could clarify what is included (e.g., version, user info). Adequate but not excellent.

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?

All three parameters have descriptions in the input schema, achieving 100% coverage. The tool description does not add extra meaning beyond what the schema already provides.

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 uses a specific verb ('Read') and resource ('bounded profile of the connected Odoo environment'), clearly distinguishing this tool from sibling tools like 'get_model_fields' or 'list_instances'.

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 such as 'health_check' or 'list_models'. An agent receives no context about prerequisites or preference conditions.

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