Clear Estimates MCP Server and API by Cotlet

List customers in Clear Estimates

clear_estimates_list_customers

Read-onlyIdempotent

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

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

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?

Beyond the readOnly/idempotent/destructive=false annotations, it discloses that the tool 'opens nothing by itself' and explains the reason browser automation is required: Clear Estimates publishes no public API. That is meaningful context an agent cannot get from annotations alone, though the exact shape of the returned guidance is only loosely described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences that cover purpose, output nature, and follow-on tooling. The closing line ('Clear Estimates's official API: Clear Estimates publishes no public API') is awkwardly worded and slightly redundant, but nothing is materially padded.

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, no output schema, and a guide-style behavior, the description supplies what an agent needs: what comes back, that nothing is executed, and which sibling tools to use next. Complete for this complexity level.

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 the baseline is 4; there is nothing for the description to disambiguate, and it does not waste space inventing parameter detail.

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 (customers in the user's Clear Estimates account) and, importantly, corrects the name's implication: the tool returns step-by-step instructions (screens, buttons, fields) rather than customer data. That distinction is explicit, though the first sentence's 'List customers' phrasing briefly reads as a data-returning action before being clarified.

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 clearly routes the agent: this tool yields the how-to, then the actual work happens via the cotlet_browser_* tools in the Cloud Browser. It does not name a when-not condition or a direct non-browser alternative, but the intended workflow and next step are unambiguous.

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

All Clear Estimates 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?