Skip to main content
Glama

booker_open

Opens a Booker page in your signed-in Cloud Browser for managing salon and spa appointments, client messages, marketing, and sales; defaults to https://signin.booker.com.

Instructions

Open a Booker page in your signed-in Cloud Browser (default https://signin.booker.com) to work with salon and spa appointments, client messages, marketing and sales.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://signin.booker.com

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?

With no annotations, the description carries the full burden. It usefully discloses that the browser is already signed in (so no auth step is needed) and that the target defaults to the sign-in URL, but it omits whether opening replaces the current page, spawns a new tab, or what is returned on success or failure.

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?

One sentence, front-loaded with the action and resource, with the default URL parenthesized inline and no redundant or filler wording.

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 one-optional-parameter navigation tool with no output schema, the description covers what the tool does, the default destination, and the signed-in session context. The remaining gap — return values and interaction with an already-open page — is modest given the tool's low complexity.

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% for the single optional 'url' parameter, so the schema already documents the field and its default. The description restates the default rather than adding format rules, accepted domains, or fallback behavior, so it adds little beyond the schema.

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 and resource — 'Open a Booker page in your signed-in Cloud Browser' — plus the default URL and the domain it serves (appointments, messages, marketing). Among siblings like booker_click, booker_read, and booker_type, this is clearly the navigation/entry tool, though it never explicitly names those siblings to sharpen the distinction.

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 description gives a purpose frame ('to work with salon and spa appointments, client messages, marketing and sales') that implies this is the starting point before clicking, reading, or typing. It does not say when to use this instead of booker_status or booker_guide, nor what happens if a page is already open.

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