Skip to main content
Glama

booker_click

Clicks a numbered element on the current Booker page to navigate or select options during appointment, client, or sales workflows in an AI agent session.

Instructions

Click a numbered element on the current Booker 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": "booker_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior1/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 discloses nothing about what a click actually does: whether it navigates, submits a form, mutates remote state, what occurs with a stale or invalid element number, or whether a wait/retry applies. For an action tool with an irreversible side effect and zero annotation coverage, this is a serious omission.

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?

A single front-loaded sentence with no wasted words. Its brevity works against it only in that it leaves no room for the usage or behavioral context an agent needs.

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?

A browser-automation click tool with no annotations and no output schema needs the description to explain post-click state (does the page change? must the agent re-read elements?) and failure modes. Almost none of that is present, leaving the agent unable to predict the result of invoking it.

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 schema already explains the element number as coming 'from the last read'. The description's 'numbered element' adds no syntax, range, or staleness guidance beyond that, so the baseline 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?

'Click a numbered element on the current Booker page' states a specific verb and resource, and 'numbered element' implicitly contrasts with the text-entry action of booker_type. It stops short of naming a sibling or scope boundary, so the differentiation requires inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no prerequisite that an element list must first be obtained (that only appears in the schema), and no mention of alternatives such as booker_type or booker_read. The phrase 'current Booker page' implies a page must already be open, but the agent must infer everything else.

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