Odoo MCP Server and API by Cotlet

List unpaid invoices in Odoo

odoo_list_unpaid_invoices

Read-onlyIdempotent

List unpaid invoices in the user's own Odoo account from ChatGPT, Claude or any AI agent. Returns how to do it in Odoo step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Odoo Cloud Browser. Odoo's official API: Yes, Odoo has an external API, but on Odoo Online it is only available on the Custom plan, not on One App Free or Standard (checked 14 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds the decisive behavioral fact that the tool 'opens nothing by itself' and requires a separate browser session to execute, plus an Odoo Online plan constraint on API access. That is real context the annotations cannot convey; the oddly dated 'checked 14 Oct 2026' note reads as unverified boilerplate.

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 behavioral core is front-loaded, but the definition is padded: 'from ChatGPT, Claude or any AI agent' adds nothing, and the closing sentence about Odoo's API availability on paid plans is justification for the design rather than instruction for invoking the tool. It could be tightened by roughly a third without losing information.

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?

With no parameters and no output schema, the description must carry the return-value burden, and it does indicate the output is a walkthrough with screens, buttons and fields. It stops short of stating the response shape or length, which is a minor gap for a zero-argument tool.

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?

The schema has zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies; nothing is missing or misdescribed on this dimension.

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 names a concrete resource (unpaid invoices) and, crucially, discloses that the tool does not retrieve invoice data but returns step-by-step instructions on how to find them in Odoo. This disambiguation is clear, though the tool name ('list unpaid invoices') sets a different expectation than the actual guide-returning behavior, which costs a point.

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 states the follow-on path explicitly: use this to get the steps, then act with the cotlet_browser_* tools in the Odoo Cloud Browser. It does not state when-not-to-use or name a direct-data alternative (e.g., an API-backed sibling), but the workflow guidance is concrete.

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

All Odoo MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?