Skip to main content
Glama

acuity_scheduling_guide

Guides AI agents through Acuity Scheduling sign-in and screens to list appointments and check availability, helping them start account tasks without an API key.

Instructions

How to work in Acuity Scheduling (list appointments and check availability): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Acuity Scheduling, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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 the content delivered (screens overview, sign-in link), which implies a read-only reference, but it never states that it performs no mutation, whether auth is required, or how the guide output should be consumed. Adequate but leaving real behavioral gaps for a no-annotation tool.

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?

Two short sentences with no filler; the scope parenthetical and the 'call this first' directive each earn their place. The core call-to-action sits at the end rather than the front, which slightly weakens front-loading but doesn't hurt 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 single-parameter guide tool with no output schema, the description covers what the guide contains and when to invoke it. It stops short of explaining how the returned guidance connects to the sibling tools or what form the output takes, which an agent would need to chain calls confidently.

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 one optional parameter (task) with 100% schema description coverage, so the schema already explains it as 'what you want done, in your words.' The description adds nothing about how to phrase the task or how it shapes the returned guidance, 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?

The description names the resource (Acuity Scheduling) and what the tool supplies: an orientation to its screens and the sign-in link, scoped in the parenthetical to listing appointments and checking availability. This distinguishes it from the sibling primitives (click/type/open/read/status), though it's slightly ambiguous whether it returns documentation or performs any action itself.

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?

'Call this first' gives explicit sequencing guidance, which is meaningful because the siblings appear to be low-level browser actions that depend on this orientation. It doesn't state when not to use it or what to do after calling it, but the primary when-to-use is unambiguous.

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