AestheticsPro MCP Server

aestheticspro_open

Opens an AestheticsPro page in your signed-in Cloud Browser so you can work with appointments and manage client contacts.

Instructions

Open a AestheticsPro page in your signed-in Cloud Browser (default https://www.aestheticspro.com/Login) to work with schedule appointments and manage client contacts.

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_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://www.aestheticspro.com/Login

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavioral fact: the browser is already signed in, so no authentication step is needed. It does not say whether opening a URL navigates away from or replaces the current page, what happens if the session has expired, or whether the page load is verified before returning.

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?

A single front-loaded sentence with no wasted clauses, and the key scoping detail (signed-in Cloud Browser) appears early. Minor grammar ('a AestheticsPro') and a slightly trailing purpose clause keep it from a 5.

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 simple navigation tool with one optional parameter, no required inputs, no output schema, and no nested objects, the description covers what the agent needs in order to call it. Additional detail on return behavior or session handling would help, but the tool's low complexity makes that a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single url parameter is already fully documented with its default, so the description need not repeat it. It does restate the same default URL, which is redundant rather than additive; baseline 3 applies.

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 states a specific verb and resource: opening an AestheticsPro page in the signed-in Cloud Browser. It is distinguishable from siblings like click, type, read, and close, since those act on an already-open page. It stops short of explicitly naming those siblings or stating that this tool must run first.

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?

The phrase 'to work with schedule appointments and manage client contacts' implies the context in which to use this tool, but no explicit when-to-use or when-not-to-use guidance is given. Nothing states that other browser tools (click, type, read) operate on the page this tool opens, so the agent must infer the sequencing.

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

Deploy Server