AestheticsPro by Cotlet

Sync appointments to Apple Calendar in AestheticsPro

aestheticspro_sync_appointments_to_apple_calendar

Read-onlyIdempotent

Sync appointments to Apple Calendar 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_sync_appointments_to_apple_calendar"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 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/idempotentHint/destructiveHint=false, and the description is consistent with them. It adds genuinely non-redundant behavior: the tool returns procedural instructions with screen/button/field detail and performs no write action itself, and it explains the API context (Enterprise-only 'Custom API solutions' at $350/month, no public docs or self-serve keys) that justifies browser automation. The odd future date '11 Nov 2026' slightly undermines the factual claim.

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 mechanism and next-step routing are front-loaded and useful, but the sentence is bloated with audience filler ('from ChatGPT, Claude or any AI agent') and a lengthy pricing/docs aside that, while relevant, could be trimmed. Splitting the mechanical instruction from the API-context note would improve scannability.

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, no-output-schema tool with strong annotations, the description covers what is returned (step-by-step instructions with screens, buttons, fields) and what to do next. Remaining ambiguity is minor — mainly how the returned steps are structured and whether the Apple Calendar side requires its own setup.

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 no parameter semantics to explain; baseline 4 applies. The description correctly implies no inputs are needed by describing a parameterless instructional lookup.

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 ('Sync appointments to Apple Calendar in the user's own AestheticsPro account') and immediately clarifies the actual mechanism: it returns step-by-step instructions rather than performing the sync. It does not name the obvious sibling (aestheticspro_sync_appointments_to_google_calendar) to distinguish the two, so differentiation is left to the reader.

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?

Gives a clear operational path: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the AestheticsPro Cloud Browser. It also states 'opens nothing by itself', preventing the agent from assuming the sync happened. It stops short of explicit exclusions (e.g. when to prefer the Google Calendar variant or the native calendar-view siblings).

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?