AestheticsPro by Cotlet

Book an appointment online in AestheticsPro

aestheticspro_book_an_appointment_online

Read-onlyIdempotent

Book an appointment online in the user's own AestheticsPro account from ChatGPT, Claude or any AI agent. Returns how to do it in AestheticsPro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's AestheticsPro Cloud Browser. AestheticsPro's official API: AestheticsPro offers "Custom API solutions" only as custom work on its $350 a month Enterprise plan, arranged with AestheticsPro, and publishes no public API documentation or self-serve API key page (checked 11 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": "aestheticspro_book_an_appointment_online"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description is consistent with them ("opens nothing by itself"). It adds value beyond the annotations by explaining why browser tools are required: no public API, only custom Enterprise API work at $350/month, checked 11 Nov 2026.

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 core behavior and the follow-up action are front-loaded in the first two sentences, with no filler. The API-plan paragraph is longer than strictly necessary for invoking the tool, but it does earn its place by preempting an agent's attempt to look for an API.

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, no output schema and full annotation coverage of the safety profile, the description supplies what is missing: what the tool returns (step-by-step screens/buttons/fields) and what it does not do. Only the differentiation from sibling booking tools remains unaddressed.

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 input parameters, so the baseline is 4. The description correctly implies no inputs are needed and does not invent or misdescribe any parameter meaning.

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 uses a specific verb and resource ("Book an appointment online in the user's own AestheticsPro account") and immediately clarifies that it returns step-by-step guidance rather than performing the booking. It does not explicitly distinguish itself from close siblings such as aestheticspro_create_appointment or aestheticspro_book_through_client_portal, so an agent must infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It does give a usage flow: call this to get screens/buttons/fields, then act with the cotlet_browser_* tools in the Cloud Browser. However, it never states when to prefer this over the actual booking siblings, nor any prerequisites or exclusions, leaving the routing decision implied.

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

All AestheticsPro 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?