Method CRM MCP Server and API by Cotlet

List overdue invoices in Method CRM

method_crm_list_overdue_invoices

Read-onlyIdempotent

List overdue invoices in the user's own Method CRM account from ChatGPT, Claude or any AI agent. Returns how to do it in Method CRM step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Method CRM Cloud Browser. Method CRM's official API: Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (checked 23 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": "method_crm_list_overdue_invoices"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: the tool "opens nothing by itself" and returns step-by-step instructions rather than invoice data. The note that Method CRM has a REST API but no official MCP server explains why a browser-driven path is needed. It stops short of describing output format or how many steps to expect.

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 core mechanic is front-loaded, but the trailing API/MCP-server sentence (with a dated parenthetical) is tangential to invoking the tool and adds bulk. The middle sentence packs two ideas (no side effects; delegate to browser tools) that could be split more cleanly.

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 correctly explains what is returned (step-by-step screens/buttons/fields) and what to do next. An agent has enough to call it and act on the result; only the precise return shape and expected step count remain unspecified.

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 tool takes zero parameters, so there is no parameter meaning to convey; baseline 4 applies. Nothing in the description misleads about inputs, and it correctly signals that no arguments are needed.

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?

States a specific verb and resource ("List overdue invoices in the user's own Method CRM account") and then clarifies the actual mechanic: it "Returns how to do it in Method CRM step by step (screens, buttons, fields) and opens nothing by itself." The name slightly overpromises (it doesn't itself list invoices), but the description corrects that. It does not distinguish itself from the guidance sibling cotlet_app_guide.

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?

It gives a clear workflow: get the steps here, then execute with the cotlet_browser_* tools in the user's Method CRM Cloud Browser. However, it never says when to prefer this over cotlet_app_guide or the other method_crm_* tools, and offers no exclusions or prerequisites.

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

All Method CRM 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?