Odoo MCP Server

Overview Schema Source Related Servers Score Discussions Admin

accounting_health_across_instances

Read-onlyIdempotent

Compare receivable or payable aging across multiple Odoo instances to identify partner health and overdue balances. Use the as-of date and top-partner filters to pinpoint risks.

Instructions

AR/AP aging fanned out across instances — the partner-network sweep

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No	Optional ISO date used as the aging reference date.
`direction`	No	Aging direction: 'receivable' or 'payable'.	receivable
`instances`	No	Optional instance selector; defaults to all eligible instances.
`top_partners`	No	Maximum top partners to include in each aging report; capped at 100.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No	Reporting tool name.
`as_of`	No
`error`	No	Sanitized error message when success is false.
`errors`	No
`results`	No
`success`	Yes	False when the call failed; see error.
`direction`	No
`elapsed_ms`	No
`instance_count`	No
`skipped_opt_out`	No
`combined_buckets`	No
`instances_queried`	No
`unknown_instances`	No
`combined_total_outstanding`	No

Schema Changelog

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

Changed18 schema fields changedv1.3.1Aug 19, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / as_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "As Of"
+}

addedOutput schema / properties / combined_buckets

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Combined Buckets"
+}

addedOutput schema / properties / combined_total_outstanding

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Combined Total Outstanding"
+}

addedOutput schema / properties / direction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Direction"
+}

addedOutput schema / properties / elapsed_ms

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Elapsed Ms"
+}

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 / errors

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Errors"
+}

addedOutput schema / properties / instance_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instance Count"
+}

addedOutput schema / properties / instances_queried

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instances Queried"
+}

removedOutput schema / properties / result

Removed value: -{
-  "additionalProperties": true,
-  "title": "Result",
-  "type": "object"
-}

addedOutput schema / properties / results

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Results"
+}

addedOutput schema / properties / skipped_opt_out

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Skipped Opt Out"
+}

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"
+}

addedOutput schema / properties / unknown_instances

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unknown Instances"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "success"
+]

changedOutput schema / title

Previous value: -"accounting_health_across_instancesOutput"New value: +"AccountingHealthAcrossInstancesResponse"

Changed4 schema fields changedv1.2.1Jul 15, 2026

addedInput schema / properties / as_of / description

Added value: +"Optional ISO date used as the aging reference date."

addedInput schema / properties / direction / description

Added value: +"Aging direction: 'receivable' or 'payable'."

addedInput schema / properties / instances / description

Added value: +"Optional instance selector; defaults to all eligible instances."

addedInput schema / properties / top_partners / description

Added value: +"Maximum top partners to include in each aging report; capped at 100."

Addedv1.0.0Jun 12, 2026

TDQS

C2.3/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, covering the safety profile. The description adds a vague hint of multi-instance scope ('fanned out across instances') but doesn't disclose additional behaviors like output aggregation or performance implications. It doesn't contradict annotations, and the annotation coverage reduces the burden, so a middling score is appropriate.

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?

The description is extremely concise (one phrase), but it's cryptic and lacks structure. It doesn't front-load a clear purpose; instead, it uses jargon ('partner-network sweep') that obscures meaning. Conciseness is present but at the expense of clarity, making it only minimally acceptable.

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?

Given the tool's complexity (multi-instance, aging direction, top-partner filtering) and the availability of an output schema, the description should explain the aggregation behavior and scope. It fails to describe what 'fanned out' means operationally, how instances are selected, or what the response contains. The schema and annotations help, but the description leaves critical gaps for correct invocation.

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% — all four parameters (as_of, direction, instances, top_partners) have detailed descriptions. The description adds no extra meaning about parameters, so the baseline of 3 applies; it neither enriches nor harms parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses cryptic language like 'fanned out across instances' and 'the partner-network sweep' without specifying that it's a read-only AR/AP aging query across multiple instances. It doesn't clearly state the resource or action, making it hard to distinguish from sibling tools like receivable_payable_aging or accounting_health_summary.

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

Usage Guidelines1/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 (e.g., single-instance aging tools or other cross-instance queries). The description gives no context for selecting it based on use case, prerequisites, or exclusions.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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