Skip to main content
Glama
Treatwell MCP Server

Treatwell MCP Server

treatwell_open

Opens a Treatwell Connect page in your signed-in Cloud Browser to manage salon appointments, clients, offers, reviews, and reports.

Instructions

Open a Treatwell page in your signed-in Cloud Browser (default https://connect.treatwell.co.uk) to work with manage salon appointments, clients, offers, reviews and reports.

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": "treatwell_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://connect.treatwell.co.uk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does add one useful behavioral fact - the browser is 'signed-in', so authentication is inherited rather than required as a separate step. Beyond that it is silent on whether navigation replaces the current page or opens a new one, whether it waits for the page to load, and what happens if the URL is invalid or the session is expired.

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 sentence with the verb and default URL front-loaded, so nothing is wasted. Minor cost: the clause 'to work with manage salon appointments' is grammatically awkward and slightly obscures the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter navigation tool with no output schema and no annotations, the definition covers the core action and default target. It is not complete enough to tell an agent what to expect afterwards (returned page state, load timing) or how navigation interacts with subsequent read/click calls, which is the main gap given output is undocumented.

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 there is only one optional parameter, so the schema already documents the url and its default. The description restates the same default URL and adds the business context of what the page is used for, which is modest added value rather than new format or constraint details.

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 ('Open') plus resource ('a Treatwell page') and the environment (signed-in Cloud Browser), and names the default URL. This is clearly distinguishable from siblings like treatwell_click, treatwell_type, treatwell_read and treatwell_close, though it never explicitly contrasts itself with them.

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?

Usage is only implied: the phrase 'to work with manage salon appointments, clients, offers, reviews and reports' suggests it is the entry point for navigating to an area before reading or clicking. There is no explicit when-to-use or when-not-to-use statement, and no mention of which sibling to call first or next.

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