Skip to main content
Glama
Pabau MCP Server

Pabau MCP Server

pabau_open

Opens a Pabau page in your signed-in Cloud Browser, defaulting to app.pabau.com, so you can view review appointment calendars and contact records for reception work.

Instructions

Open a Pabau page in your signed-in Cloud Browser (default https://app.pabau.com) to work with review appointment calendars and contact records for reception work.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.pabau.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 burden. It usefully states the browser is "signed-in" (implying an existing authenticated session) and gives the default URL, but says nothing about whether it opens a new tab or navigates the current one, what happens if the page is already open, failure/timeout behavior, or whether page content is returned.

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?

One front-loaded sentence with the verb and default URL stated up front. The trailing clause about "reception work" is mildly decorative but does convey intended use, so waste is minimal.

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 navigation tool with no output schema, the description covers the what and the default but omits the outcome an agent most needs: whether a successful call returns page content or merely loads the page. Adequate but with a clear informational gap.

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% and the single url parameter already documents the same default value, so the description adds no syntax, relative-URL, or domain-restriction 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?

Uses a specific verb ("Open") plus a specific resource ("a Pabau page in your signed-in Cloud Browser") and names the default target. It is clearly distinguishable from siblings like pabau_click or pabau_read, though it doesn't explicitly say how it differs from them.

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 phrase "to work with review appointment calendars and contact records for reception work" implies this is the entry step before interacting with the page, but there is no explicit when-to-use/when-not guidance or reference to an alternative sibling. An agent must infer that this should precede click/type/read calls.

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