Skip to main content
Glama

booker_guide

Find how to navigate Booker screens, appointments, client messages, marketing, and sales, and get the sign-in link before using other Booker MCP actions.

Instructions

How to work in Booker (salon and spa appointments, client messages, marketing and sales): 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": "booker_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/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 behavioral burden. Calling it a 'guide' implies orientation rather than mutation, and it discloses that the guide covers screens and the sign-in link, but it does not explicitly state side effects, auth requirements, or what the response looks like.

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?

The description is two short sentences with no wasted wording. The primary purpose and covered domains are front-loaded, followed by the important 'Call this first' routing instruction.

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-parameter guide tool with no output schema, the description gives enough context about what the guide contains and when to call it. It could be slightly stronger by explicitly saying this returns guidance rather than performing Booker actions.

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?

The single optional 'task' parameter has complete schema description coverage, so the schema already explains its meaning. The description does not mention the parameter at all, so baseline 3 is appropriate.

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 clearly identifies this as a Booker orientation guide covering screens and the sign-in link, and names the product domains (appointments, messages, marketing/sales). It does not explicitly distinguish itself from sibling action tools such as booker_status, but 'Call this first' gives useful routing context.

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?

The instruction 'Call this first' is an explicit usage rule for when to invoke this tool before the sibling interaction tools. It does not provide when-not-to-use conditions or name alternatives, which keeps it below a 5.

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