ERPNext MCP Server and API by Cotlet

List overdue invoices in ERPNext

erpnext_list_overdue_invoices

Read-onlyIdempotent

List overdue invoices in the user's own ERPNext account from ChatGPT, Claude or any AI agent. Returns how to do it in ERPNext step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ERPNext Cloud Browser. ERPNext's official API: Yes.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the tool 'opens nothing by itself' and returns procedural instructions (screens, buttons, fields) rather than mutating or querying anything, which prevents an agent from expecting a side effect or a data payload.

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?

Two sentences, front-loaded with the resource, but 'from ChatGPT, Claude or any AI agent' is promotional filler and the trailing fragment 'ERPNext's official API: Yes.' is ambiguous and adds no actionable meaning.

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?

For a zero-parameter guidance tool with no output schema, the description covers what comes back ('step by step – screens, buttons, fields') and what to do next. What remains unclear is whether the overdue invoice list itself ever surfaces as tool output or only through the browser tools.

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

Parameters5/5

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

Zero parameters with 100% schema coverage; there is nothing parameter-level left to explain, and the description correctly does not invent or discuss inputs.

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 the resource (overdue invoices in the user's ERPNext account) and, critically, clarifies the actual verb: it returns a step-by-step how-to rather than the invoice data. However, the first sentence ('List overdue invoices...') and the tool name reinforce a data-retrieval reading that the second sentence only partially corrects, leaving a small ambiguity about whether any invoices are actually returned.

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 workflow guidance: use this first to get ERPNext steps, then execute them with the cotlet_browser_* tools in the user's ERPNext Cloud Browser. It does not name a when-not condition or an alternative invoicing tool, but the handoff to the browser tool family is a concrete usage path.

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

All ERPNext 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?