Skip to main content
Glama
Pabau MCP Server

Pabau MCP Server

pabau_click

Clicks a numbered element on the current Pabau page to select controls or navigate records after reading the page. Use the element number from the last read to target the intended item.

Instructions

Click a numbered element on the current Pabau 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": "pabau_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.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says what is clicked and that the number comes from the last read, but it does not disclose side effects such as navigation, form submission, or whether clicking is irreversible, nor what happens if the referenced element is stale.

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 a single, front-loaded sentence with no padding. Every phrase contributes to identifying the action and the referenced element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a stateful interaction tool with no annotations and no output schema. The description omits important context for safely invoking a click, including side effects, failure modes for stale element numbers, and what the agent should do afterward.

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 parameter is already described as the element number from the last read. The description restates that meaning without adding format, constraints, or error behavior beyond the schema, so the baseline score of 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 states a specific action and target: click a numbered element on the current Pabau page. It is clearly distinct from sibling operations like typing, reading, opening, or closing, though it does not explicitly contrast 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 Guidelines3/5

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

Usage is implied: the element number comes from the last read, and the action applies to the current page. The description does not state when to prefer clicking over typing, opening, or other alternatives, nor does it describe prerequisites such as ensuring the page is loaded or the element is still valid.

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