Odoo MCP Server

Overview Schema Source Related Servers Score Discussions Admin

receivable_payable_aging

Read-onlyIdempotent

Produce an aged receivable or payable report, categorizing open items by overdue days. Set the as-of date, direction, and top partners to focus the analysis.

Instructions

Aged receivable/payable report bucketed by days overdue

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No	Optional ISO date used as the aging reference date.
`limit`	No	Maximum open-item lines to inspect.
`instance`	No	Optional configured Odoo instance name; uses the default if omitted.
`direction`	No	Aging direction: 'receivable' or 'payable'.	receivable
`top_partners`	No	Maximum top partners to include; 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.
`buckets`	No
`success`	Yes	False when the call failed; see error.
`partners`	No
`direction`	No
`truncated`	No
`line_count`	No
`partner_count`	No
`skipped_lines`	No
`total_outstanding`	No

Schema Changelog

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

Changed16 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 / buckets

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

addedOutput schema / properties / direction

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

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

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

addedOutput schema / properties / partner_count

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

addedOutput schema / properties / partners

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

removedOutput schema / properties / result

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

addedOutput schema / properties / skipped_lines

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

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

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

addedOutput schema / properties / truncated

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

changedOutput schema / required

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

changedOutput schema / title

Previous value: -"receivable_payable_agingOutput"New value: +"ReceivablePayableAgingResponse"

Changed5 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 / instance / description

Added value: +"Optional configured Odoo instance name; uses the default if omitted."

addedInput schema / properties / limit / description

Added value: +"Maximum open-item lines to inspect."

addedInput schema / properties / top_partners / description

Added value: +"Maximum top partners to include; capped at 100."

Addedv1.0.0Jun 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive, so the description doesn't contradict them. The description provides a good high-level behavior ('bucketed by days overdue') that complements annotations. However, it doesn't elaborate on side effects (though readOnly implies none) or specific data aggregation behavior, but given the annotations, this is adequate.

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

Conciseness4/5

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

The description is one sentence, concise and to the point. It communicates the core function without fluff. It could maybe expand on the output, but for a report tool, this is appropriately short.

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?

The description is minimal but an output schema is present, so return values don't need explanation. However, it doesn't mention the meaning of 'open-item lines' or the purpose of the 'limit' parameter, which could be ambiguous. The tool complexity is moderate (5 params, all documented), so more context would help. Given the output schema exists, it's acceptable but could be slightly more complete.

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

Parameters4/5

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

All parameters have descriptive schema descriptions: as_of (ISO date), limit (max lines), instance (optional Odoo instance), direction (receivable/payable), top_partners (max partners, capped). The description adds context by saying the report is 'bucketed by days overdue', which helps understand what 'as_of' and 'direction' mean. Since schema coverage is 100%, the parameter semantics are already well-covered, but the description reinforces the purpose.

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?

The description clearly states the tool produces an 'Aged receivable/payable report' with a specific structure (bucketed by days overdue). It effectively conveys the core purpose and distinguishes it from general reporting tools. However, it doesn't explicitly differentiate from sibling tools like `accounting_health_summary` or `business_pack_report`, which might also involve financial reports.

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 generating aging reports but provides no guidance on when to choose this over alternatives or prerequisites (e.g., configured Odoo connection, instance). Given sibling tools like `accounting_health_summary`, explicit when-to-use guidance is missing. The schema mentions 'instance' and 'direction', but the description doesn't clarify typical use cases.

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