Skip to main content
Glama
Sign In

Clear Estimates MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create estimate in Clear Estimates

clear_estimates_create_estimate
Read-onlyIdempotent

Create estimate 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_create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and the description explains why, which is genuinely valuable: the tool 'opens nothing by itself' and returns screens, buttons, and fields. It also discloses the API situation (no public API). It stops short of detailing the exact return structure, so not quite a 5.

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 concise sentences that front-load the core behavior and then the follow-up instructions. 'from ChatGPT, Claude or any AI agent' is mild filler, and the final API sentence is awkwardly phrased, but overall it is tight and well ordered.

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 guide tool with no output schema, the description covers what it returns, what it does not do, and how to proceed. The return value is described in enough detail that an agent knows what to expect; only finer format detail is absent.

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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter detail is possible or 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 ('Create estimate in the user's own Clear Estimates account') and immediately clarifies the real behavior: it returns step-by-step instructions rather than creating anything. This distinguishes it from the cotlet_browser_* tools. Slightly muddled because the leading verb 'Create' suggests a mutation that the tool doesn't actually perform.

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?

Explicitly describes the follow-up workflow: use this to get the steps, then perform them with cotlet_browser_* in the user's Cloud Browser. It names the alternative tool family and the context that selects it. It doesn't spell out when to prefer this over other Clear Estimates helpers, but the context is clear.

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 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