AestheticsPro by Cotlet

View scheduling changes and availability in AestheticsPro

aestheticspro_view_scheduling_changes_and_availability

Read-onlyIdempotent

View scheduling changes and availability 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_view_scheduling_changes_and_availability"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with all of them, explicitly stating the tool opens nothing itself. It adds real context beyond the annotations: the return shape is procedural instructions rather than data, and the API-availability note explains why browser automation is the route. It does not describe the granularity or format of the returned steps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action sentence, then the execution handoff, then the API caveat. The Enterprise-plan pricing and 'checked 11 Nov 2026' parenthetical is verbose but is the only part that carries justification for the browser-tool routing rather than being filler.

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, read-only, no-output-schema tool, the description covers what the tool returns (step-by-step screens, buttons, fields), what it does not do (open anything), and how to complete the action with browser tools. What remains unspecified is how 'scheduling changes and availability' differs from the calendar and Book Now availability siblings.

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 schema imposes no documentation burden and the baseline is 4. The description correctly implies no inputs are needed to request the walkthrough.

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?

Names a specific verb and resource: view scheduling changes and availability in the user's own AestheticsPro account, and scopes it to the user's own tenant. It does not differentiate from nearby siblings such as aestheticspro_view_appointment_calendar or aestheticspro_view_book_now_availability, which also surface availability information, 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?

Gives a clear workflow instruction: this tool only returns step-by-step screens/buttons/fields and 'opens nothing by itself,' after which the agent should act via cotlet_browser_* tools in the Cloud Browser. That is genuine when-to-use guidance plus an execution handoff. It stops short of naming when to prefer a direct-view sibling instead.

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?