Skip to main content
Glama
Sign In

Clear Estimates MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Add template to estimate in Clear Estimates

clear_estimates_add_template_to_estimate
Read-onlyIdempotent

Add template to 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_add_template_to_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description is consistent with that. It usefully adds that the tool returns guidance and opens nothing, plus notes there is no public API, but it does not describe the shape of the returned steps or any failure modes.

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 points are front-loaded, but the trailing clause 'Clear Estimates's official API: Clear Estimates publishes no public API' is grammatically awkward and slightly redundant, and the sentence is dense. It is serviceable but not tight.

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 guidance tool with no output schema, the description adequately conveys what it returns (steps referencing screens, buttons, fields), what it does not do, and which tools to use next. Minor gaps remain around the returned structure and prerequisites.

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?

There are zero parameters and the schema is fully covered, so per the baseline this is a 4. The description correctly does not waste space restating param semantics.

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 specific verb and resource (add template to estimate in the Clear Estimates account) and then clarifies the crucial nuance that it returns step-by-step instructions rather than performing the action. That distinguishes it from the cotlet_browser_* tools, though it does not name any non-browser siblings.

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 gives clear sequencing: call this to get the step-by-step how-to, then carry it out with the cotlet_browser_* tools in the user's Cloud Browser. It also notes the tool 'opens nothing by itself,' making the division of labor explicit, but it does not cover edge cases such as when the template already exists.

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