Skip to main content
Glama
Treatwell MCP Server

Treatwell MCP Server

treatwell_guide

Explains how to manage salon appointments, clients, offers, reviews, and reports in Treatwell, including key screens and the sign-in link. Use it first to find the right workflow.

Instructions

How to work in Treatwell (manage salon appointments, clients, offers, reviews and reports): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Treatwell, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It partially meets it by disclosing the response content (screens and the sign-in link), which implies a read-only informational tool, but it never explicitly states that nothing is created or modified in Treatwell, and 'manage salon appointments...' could be misread as performing management rather than explaining it.

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?

Two short clauses with no wasted words, and the covered domains are grouped compactly in a parenthetical. The key directive 'Call this first' is placed at the end rather than front-loaded, which slightly weakens scannability.

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-optional-parameter tool with no output schema, the description covers subject matter and call ordering. It is still unclear what form the answer takes (step-by-step instructions, screen names, a link), whether the 'task' input narrows the guidance, and how the result connects to the sibling action tools.

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?

There is a single optional 'task' parameter with 100% schema description coverage ('What you want done in Treatwell, in your words'). The description adds no guidance on how to phrase that task or what effect it has on the returned guidance, so the baseline of 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 identifies the resource clearly ('How to work in Treatwell') and enumerates the covered domains (appointments, clients, offers, reviews, reports) plus what it returns ('its screens and the sign-in link'). It is distinguishable from siblings as an orientation/guide tool, though the verb phrase is softer than a concrete action verb.

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?

'Call this first' gives explicit ordering guidance relative to the other treatwell_* tools, which is the key routing decision for a guide tool. It stops short of saying when not to call it or what to do after (e.g. whether the result is sufficient to act or must be followed by treatwell_open/click).

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