Skip to main content
Glama

acuity_scheduling_open

Opens an Acuity Scheduling page in your signed-in cloud browser to list appointments and check availability without an API key.

Instructions

Open a Acuity Scheduling page in your signed-in Cloud Browser (default https://secure.acuityscheduling.com) to work with list appointments and check availability.

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": "acuity_scheduling_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://secure.acuityscheduling.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the important behavioral fact that the page opens in a "signed-in Cloud Browser," meaning the session is already authenticated and shared. However, it says nothing about what happens to existing page state, whether a handle or confirmation is returned, or how subsequent tools target the opened page.

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 filler, and the default value is surfaced early. Minor flaws: the article error ("a Acuity") and the slightly garbled "to work with list appointments" phrasing reduce polish without hurting comprehension.

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 simple one-optional-param, no-output-schema tool this is close to sufficient, but it leaves open the key follow-up question of how the opened page is referenced by the other browser tools. A sentence on the returned handle or on state persistence would close the 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?

There is only one optional parameter and schema description coverage is 100%, with the schema already documenting the default. The description merely repeats the default URL, adding no new meaning (accepted formats, allowed domains, query strings).

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 concrete verb ("Open") and resource ("Acuity Scheduling page") plus the default URL, so the agent knows exactly what action occurs. It contrasts implicitly with siblings like acuity_scheduling_close and acuity_scheduling_read, but never names them or draws the boundary explicitly.

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 list appointments and check availability" hints at workflow context, implying you open first and then use read/click, but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. An agent must infer ordering from sibling names rather than from the description.

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