AutoLeap MCP Server and API by Cotlet

Book appointment in AutoLeap

autoleap_book_appointment

Read-onlyIdempotent

Book appointment 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_book_appointment"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself' and adds genuinely new context — that the output is a procedural how-to and that execution requires the browser tools. The note about the gated Partner API explains why the browser path is required, which annotations cannot convey.

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?

Core behavior is front-loaded, but the opening clause about ChatGPT, Claude or any AI agent is filler, and the closing paragraph on the Partner API is long and includes a dated check ('checked 28 Oct 2026') that reads as justification rather than actionable guidance. The essential instructions could be stated in roughly half the space.

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 and no output schema, the description correctly carries the burden of explaining the return value (step-by-step screens, buttons, fields) and the follow-up execution path. It is nearly complete for a guidance-style tool; only the relationship to cotlet_app_guide is left unstated.

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, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description does not pretend otherwise or introduce unstated inputs.

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?

Description states a specific verb and resource (book an appointment in the user's AutoLeap account) and clarifies an important nuance — the call returns step-by-step instructions (screens, buttons, fields) rather than performing the action. That nuance partly contradicts the imperative name, but the text resolves it explicitly, so an agent knows what it gets back.

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 a clear usage flow: call this to get the steps, then execute them with the cotlet_browser_* tools in the AutoLeap Cloud Browser. It does not contrast itself against the sibling cotlet_app_guide, so an agent must infer whether the general app guide is an alternative, but the workflow context is strong.

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

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

Need Help?