Dubsado MCP Server and API by Cotlet

List unpaid invoices in Dubsado

dubsado_list_unpaid_invoices

Read-onlyIdempotent

List unpaid invoices in the user's own Dubsado account from ChatGPT, Claude or any AI agent. Returns how to do it in Dubsado step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Dubsado Cloud Browser. Dubsado's official API: Dubsado has no public API (checked 11 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": "dubsado_list_unpaid_invoices"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself,' which is genuinely reassuring for a browser-adjacent tool. It also discloses the return shape (steps, screens, buttons, fields) and the constraint that Dubsado has no public API, adding context beyond the structured fields.

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 behaviour is front-loaded, but the opening phrase 'from ChatGPT, Claude or any AI agent' is promotional filler, and the closing line 'Dubsado's official API: Dubsado has no public API (checked 11 Oct 2026)' is awkwardly worded and cites a future date that reads as noise. Both could be cut without losing information.

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 zero-parameter, read-only guide tool with rich annotations and no output schema, the description covers what it returns, what it does not do (open anything), and how to proceed afterwards. Nothing an agent needs in order to invoke it correctly is missing.

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 semantics to document and the baseline is 4. The description correctly implies no inputs are required, and the empty schema is self-explanatory.

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 makes clear that despite the name, the tool returns a step-by-step procedure (screens, buttons, fields) rather than the invoice data itself: 'Returns how to do it in Dubsado step by step ... and opens nothing by itself.' That is a specific and useful clarification, though the name/behaviour mismatch means an agent must read the description to know what it actually gets back.

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 explicitly routes the agent onward: do the work 'with the cotlet_browser_* tools in the user's Dubsado Cloud Browser,' which is a concrete next step rather than an inference. It does not name when NOT to use it (e.g. versus cotlet_app_guide or the dubsado_* action siblings), so it falls short of full alternative coverage.

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

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