Skip to main content
Glama

acuity_scheduling_click

Clicks a numbered element on the current Acuity Scheduling page so an agent can interact with appointments, appointment types, or time slots using the element number from the last read.

Instructions

Click a numbered element on the current Acuity Scheduling 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": "acuity_scheduling_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.4/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, yet it only says what is clicked, not what happens afterward (navigation, form submission, new page state) or what occurs on an invalid element number. The only behavioral disclosure is that the action targets the 'current' page, which is minimal for an action tool with side effects.

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?

A single sentence with the action front-loaded and no filler; every word contributes to specifying what is clicked and where.

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?

One parameter fully documented by the schema and no output schema to explain keeps the burden low, and the description covers what is clicked and that it operates on current page state. It remains thin on post-click effects and failure behavior for an unannotated action tool.

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 schema already explains that 'element' is the 'Element number from the last read.' The description restates that implicitly ('numbered element') without adding syntax, range, or lifecycle details beyond what the schema supplies, so 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?

States a specific verb ('Click') and an object ('a numbered element on the current Acuity Scheduling page'), which is concrete enough for an agent to act on. It doesn't differentiate itself from siblings like acuity_scheduling_read or acuity_scheduling_guide, though 'numbered element' implicitly ties to the read tool.

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 'numbered element' plus the schema note 'Element number from the last read' implies the tool must follow a read call, so usage is implied rather than stated. There is no explicit when-to-use/when-not guidance or mention of which sibling supplies the numbering.

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