Skip to main content
Glama
Pabau MCP Server

Pabau MCP Server

pabau_guide

Provides instructions for navigating Pabau reception workflows—signing in, checking appointment calendars, and reviewing contact records—so agents know how to proceed before other actions.

Instructions

How to work in Pabau (review appointment calendars and contact records for reception work): 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": "pabau_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Pabau, 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 must carry behavioral disclosure. It implies a read-only informational tool and indicates what it surfaces (screens, sign-in link), which is useful, but it says nothing about side effects, whether the task argument changes the response, or any limits on repeated calls.

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 compact sentences with no filler, and the scope is front-loaded in the parenthetical. The critical "Call this first" cue sits at the end rather than leading, a minor structural miss for a routing instruction.

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, no-output-schema orientation tool this is close to sufficient, and the description does say what the tool provides. It leaves unclear whether the `task` argument is optional (required count is 0) and whether the guide output varies by task, which an agent would want to know before calling.

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 single `task` parameter is already documented as "What you want done in Pabau, in your words." The description never references the parameter, so it adds no meaning beyond the schema; 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 the resource (Pabau) and scopes it with a parenthetical ("review appointment calendars and contact records for reception work"), plus concrete contents ("its screens and the sign-in link"). This makes it distinguishable from the action-oriented siblings like pabau_click and pabau_type, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this first" is an explicit, unambiguous ordering instruction that tells the agent when to invoke it relative to everything else. It stops short of stating exclusions or what to do on subsequent calls, so it is not a full when/when-not treatment.

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