Skip to main content
Glama
Sign In

EstimateOne MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update Watchlist in EstimateOne

estimateone_update_watchlist
Read-onlyIdempotent

Update Watchlist 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_update_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations: it returns screen, button, and field instructions and opens nothing by itself. This aligns with readOnlyHint=true and destructiveHint=false and clarifies that actual changes require the browser tools. It does not discuss authentication or rate limits, but those are less relevant for a zero-parameter instructional tool.

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 is stated clearly, but the description includes unnecessary phrasing such as 'from ChatGPT, Claude or any AI agent' and an oddly specific API check date. The useful caveat that nothing opens automatically and that browser tools are needed is present, but the wording could be tighter and more front-loaded.

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, read-only guidance tool, the description provides enough detail to understand what it returns and what the agent must do next. It does not need an output schema because the response format is described as step-by-step instructions. Minor details about the exact level of guidance could be clearer, but nothing essential 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 has zero parameters, so there is no parameter semantics to document. The schema is empty and the description correctly does not introduce any parameter behavior.

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 explains that the tool provides step-by-step instructions for updating the user's own EstimateOne watchlist rather than performing the update itself. It clearly says it opens nothing by itself, which resolves the tension between the tool name and its actual read-only behavior.

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 tells the agent to use this tool to get the procedure and then use cotlet_browser_* tools to carry it out. It also explains why the official API is not an option because it is not self-service and is read-only. The guidance is clear, though it does not explicitly list when not to use this tool beyond the API note.

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