Skip to main content
Glama

acuity_scheduling_read

Read the current Acuity Scheduling page to capture visible text, numbered buttons, links, and fields; optionally inspect one element for targeted analysis.

Instructions

Read the current Acuity Scheduling page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

No annotations are provided, so the description carries the full burden. It does add real behavioral value by disclosing that elements come back numbered and typed as buttons, links and fields, implying an indexed snapshot usable by follow-up actions. It omits whether reading mutates state, whether the page must already be open, and what happens on navigation errors or timeouts.

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?

One front-loaded sentence with no filler, and the verb-plus-resource leads. The trailing enumeration ("its text and numbered buttons, links and fields") is slightly compressed and grammatically loose, costing a bit of precision rather than length.

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 an unannotated read tool with no output schema and one optional param, the description covers what is returned but not the output shape, ordering, or how the numbered elements connect to acuity_scheduling_click and acuity_scheduling_type — the workflow linkage an agent most needs. Adequate, but with a clear gap for a multi-tool browser-automation set.

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 single optional parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no information about the element parameter — scope semantics such as whether it reads the subtree only, and how element numbers relate to button numbers, are left unstated.

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 ("read") and resource ("the current Acuity Scheduling page") and enumerates returned content: text, numbered buttons, links, fields. This is clearly distinguishable from navigation-oriented siblings like open/close, though it never names a sibling or states how it pairs with click/type.

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?

Usage is only implied by the word "current" — an agent infers this returns the present page state rather than navigating. There is no explicit when-to-use vs when-to-use-instead guidance (e.g., versus acuity_scheduling_status or acuity_scheduling_guide), and no stated preconditions such as requiring an open page first.

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