AestheticsPro by Cotlet

Set appointment reminder timing in AestheticsPro

aestheticspro_set_appointment_reminder_timing

Read-onlyIdempotent

Set appointment reminder timing 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_set_appointment_reminder_timing"
  }
}

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 declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: the output is procedural guidance (screens, buttons, fields) and the tool "opens nothing by itself," resolving the apparent tension between "set" and readOnlyHint. The API-plan note explains why a browser path is required. Return format details (e.g., structure of the step list) are absent, keeping it below a 5.

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 operational content is front-loaded in one efficient sentence, but the closing paragraph about AestheticsPro's Enterprise API pricing and docs status is lengthy rationale that does not change how an agent invokes the tool. It is defensible context but not tightly earned.

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-param, read-only guidance tool with no output schema, the definition covers what it returns, that it makes no changes, and the follow-up execution path. Only the exact structure of the returned steps 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?

Zero parameters, so the baseline is 4. The description correctly implies no input is needed, though it doesn't say how appointment/reminder selection is conveyed given the empty schema.

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?

"Set appointment reminder timing" is a specific verb+resource, and the description immediately clarifies that the tool returns step-by-step instructions rather than performing the change. It does not explicitly contrast with nearby siblings like aestheticspro_choose_reminder_channel or aestheticspro_configure_appointment_confirmations, so an agent must infer the boundary.

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 workflow: get the guidance here, then execute it with cotlet_browser_* tools in the Cloud Browser, and states that nothing is opened by this call. What's missing is an explicit when-not or a named alternative for related reminder tasks.

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?