Skip to main content
Glama
Sign In

EstimateOne MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List leads in EstimateOne

estimateone_list_leads
Read-onlyIdempotent

List leads in the user's own EstimateOne account from ChatGPT, Claude or any AI agent. Returns how to do it in EstimateOne step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's EstimateOne Cloud Browser. EstimateOne's official API: EstimateOne has an External API, but it is not self-service and it is read-only (checked 6 Nov 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": "estimateone_list_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world; the description adds real value by disclosing that the tool performs no browser action and returns procedural instructions rather than lead data. It also discloses why browser automation is required (the official External API is not self-service and is read-only), which is context an agent cannot get from annotations.

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 behavior and the handoff to cotlet_browser_* are front-loaded, which is good, but the closing sentence about the official External API is tangential and contains a confusing future-dated check ('6 Nov 2026'), slightly weakening an otherwise tight definition.

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 rich annotations, the main remaining question is what comes back; the description answers that by specifying step-by-step screens, buttons and fields, and names the tools to use afterward. Only the lack of sibling differentiation keeps it from being fully complete.

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?

Zero parameters, so the baseline is 4. The description correctly implies no inputs are needed and does not waste space restating an empty schema.

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 a concrete outcome (a step-by-step guide of screens, buttons and fields for listing leads in EstimateOne) and explicitly says it 'opens nothing by itself', which resolves the ambiguity created by the 'list_leads' name. It does not differentiate itself from the other estimateone_* siblings such as search_tenders or get_tender_details, which keeps it short of a 5.

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: call this first to get the procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. That is useful routing, but there is no explicit guidance on when to choose this versus other EstimateOne listing/search tools, and no stated 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 EstimateOne MCP Server and API by Cotlet toolsInspect
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