Skip to main content
Glama
Odoo MCP Server

Odoo MCP Server

by rizkyagung18

get_unpaid_invoices

Read-only

List posted customer invoices that remain unpaid, ordered by oldest due date, and show amount due plus days overdue to identify who owes money and which invoices are overdue.

Instructions

List posted customer invoices that are not (fully) paid, oldest due date first.

Includes amount still due and days overdue. Use for "who owes us money?" or "which invoices are overdue?".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_unpaid_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return (1-50).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish this as a read-only, closed-world operation. The description adds useful behavioral detail beyond annotations: it only includes posted invoices that are not fully paid, returns oldest due date first, and includes amount still due and days overdue.

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 short, front-loaded, and every sentence contributes either filtering criteria, output detail, or usage guidance. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one well-documented parameter, annotations, and an output schema, the description covers purpose, filtering, sorting, included fields, and usage examples. Nothing essential for correct invocation is missing.

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?

The only parameter is fully described in the schema, including default and min/max constraints. The description does not add meaning about the limit parameter, so a baseline 3 is appropriate when schema coverage is 100%.

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 states a specific verb and resource: list posted customer invoices that are not fully paid. It also adds scope and sort order (oldest due date first), making the tool clearly identifiable against unrelated siblings.

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

Usage Guidelines4/5

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

It gives explicit use cases, such as answering 'who owes us money?' and 'which invoices are overdue?'. It does not name when not to use it or an alternative, but no relevant sibling is obvious from the supplied context.

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