Skip to main content
Glama

Pabau by Cotlet

Hide client details on the calendar display in Pabau

pabau_hide_client_details_on_the_calendar_display
Read-onlyIdempotent

Hide client details on the calendar display in the user's own Pabau account from ChatGPT, Claude or any AI agent. Returns how to do it in Pabau step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Pabau Cloud Browser. Pabau's official API: Pabau publishes an official API for selected business operations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare a safe, non-destructive read, and the description is consistent with them by stating the tool 'opens nothing by itself' and only returns instructions. That clarifies the side-effect boundary between planning and acting, though it says little about the shape or length of the returned guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentences are front-loaded and useful, but the final sentence about Pabau's official API is filler that does not help an agent decide or act. The opening sentence is also somewhat is repetitive in restating the title verbatim.

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?

There is no output schema, so the description correctly explains what comes back (step-by-step instructions). Nothing about the calling contract is missing for a zero-parameter guidance tool, though it could hint at the size of the returned procedure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema accepts zero parameters, which is the correct baseline, and there is nothing parameter-related for the description to explain. The description adds no parameter detail, but it also has no parameters to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific configuration task (hiding client details on the calendar display) inside a named product, and states exactly what the tool returns: step-by-step instructions with screens, buttons, and fields. It explicitly distinguishes itself from the browser siblings by saying it 'opens nothing by itself' and that the action is then performed with the cotlet_browser_* tools.

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 usage flow is clear: call this first to get instructions, then execute them with the cotlet_browser_* tools in the user's Pabau Cloud Browser. It states the context (the user's own Pabau account) but gives no explicit exclusions or a case where a different tool would be preferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources