Skip to main content
Glama
odoo-mcp

odoo-mcp

by affifariza04

overdue_invoices

Read-only

Retrieves posted customer invoices that are past due and not fully paid, sorted by most overdue first; optionally filters by an as-of date.

Instructions

Posted customer invoices past their due date that are not fully paid, most overdue first.

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": "overdue_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful filtering semantics (only 'posted' invoices, only not-fully-paid, sorted most-overdue-first), but says nothing about result limits, pagination, or how partial payments affect inclusion.

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?

One short sentence, front-loaded with the resource and scope, ending with sort order. No filler or redundant restatement of the tool name.

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?

This is a simple read-only query with an output schema, so return-value explanation is unnecessary and the filtering scope is well covered. The remaining gap is the undefined as_of parameter, which is the one thing an agent must understand to call it correctly.

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

Parameters2/5

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

There is a single parameter, as_of, with 0% schema description coverage, and the description never mentions it. The agent cannot learn from either source whether as_of sets the reference date for the overdue calculation or what a null default means, so the description leaves the only parameter unexplained.

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 states a precise resource and scope: posted customer invoices that are past due and not fully paid, returned most overdue first. An agent can tell exactly what dataset comes back, though the leading verb is implicit (a noun phrase) and it never contrasts with siblings like sales_report or search_records.

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?

Usage is implied by the filter conditions (you call it when you want overdue, unpaid, posted invoices), but there is no explicit when-to-use or when-not guidance and no pointer to an alternative for related queries.

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