Skip to main content
Glama
Treatwell MCP Server

Treatwell MCP Server

treatwell_click

Clicks a numbered element on the current Treatwell page to perform precise actions like managing bookings or offers after reading the page.

Instructions

Click a numbered element on the current Treatwell page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "treatwell_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'click' but not whether the click navigates, submits, or destroys state, whether it blocks until the page settles, what happens on an invalid element number, or what the caller should do next (e.g., re-read). For an unannotated browser-mutation tool this is a substantial gap.

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?

A single front-loaded sentence with no filler; the action and target are stated immediately and nothing is redundant.

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?

The tool is low-complexity (one required integer, no output schema), so the description need not be long, but it leaves open the post-click contract: whether a follow-up read is required, whether page state changes, and how failures surface. Adequate but with clear gaps given the absence of annotations.

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 description coverage is 100%, and the schema already states 'Element number from the last read' with a minimum of 1. The description's phrase 'numbered element' adds essentially nothing beyond that, so the 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 names a specific verb ('Click') and a specific resource ('a numbered element on the current Treatwell page'), so an agent knows exactly what action this performs. It does not, however, contrast itself with siblings like treatwell_type or treatwell_open, which is what would be needed for a 5.

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: 'numbered element' plus the schema note 'Element number from the last read' hints that a treatwell_read must precede this call. There is no explicit statement of when to choose click over treatwell_type or treatwell_open, and no exclusion conditions.

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