Skip to main content
Glama
Sign In

AutoLeap MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Send estimate in AutoLeap

autoleap_send_estimate
Read-onlyIdempotent

Send estimate in the user's own AutoLeap account from ChatGPT, Claude or any AI agent. Returns how to do it in AutoLeap step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's AutoLeap Cloud Browser. AutoLeap's official API: AutoLeap has a REST Partner API, but it is gated: credentials go to approved integration partners, and AutoLeap describes it as not available for the Essentials, Pro and Elite plans (checked 28 Oct 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": "autoleap_send_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?

The annotations already establish that this is a non-destructive, read-only, idempotent operation, and the description adds useful context by saying it 'opens nothing by itself' and returns screens, buttons, and fields. The API gating note further explains why direct API use is not an option.

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?

The key point—that this tool returns instructions rather than sending anything—is front-loaded, and the follow-up browser execution guidance is useful. The API gating sentence is somewhat long but still relevant context for why the browser path is needed.

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, the description is sufficiently complete: it says what is returned, what is not done, and how to proceed afterward. More detail on the exact return format could help, but the essential behavior is covered.

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 are no input semantics to document beyond the empty schema. The baseline score of 4 is appropriate because the description does not need to compensate for missing parameter information.

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 clearly states that the tool returns step-by-step instructions for sending an estimate rather than performing the send itself, which resolves the ambiguity in the tool name. It distinguishes this guidance role from the actual browser actions performed by cotlet_browser_* tools.

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 explains that the agent should use this tool first to get the AutoLeap steps, then carry them out with cotlet_browser_* tools. It does not name other AutoLeap alternatives, but the primary when-to-use split between guidance and browser execution is clear.

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

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