Skip to main content
Glama

acuity_scheduling_type

Type text into a numbered field on the current Acuity Scheduling page, enabling agents to fill in forms or inputs during an active session.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "acuity_scheduling_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

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?

With no annotations, the description carries the full disclosure burden. It correctly scopes the action to the current page and ties indices to the last read, but says nothing about whether typing replaces or appends to existing content, whether it triggers blur/submit events, or what errors occur for an invalid field number.

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 front-loaded sentence with no padding; the target of the action is stated before any qualifiers.

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?

For a two-parameter, no-annotation, no-output-schema interaction tool, this covers the essentials: what it does, where it acts, and how the field number relates to prior reads. The remaining gap is mutation semantics (replace vs append), which is a modest omission rather than a blocking one.

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%, so both parameters are already documented in the schema. The description's wording ("numbered field", "type text") mirrors those definitions without adding format rules, valid ranges, or index-staleness caveats beyond the schema.

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 pairs a specific verb ("Type text") with a specific target ("a numbered field on the current Acuity Scheduling page"), which is enough to separate it from click/read/close siblings by action type. It stops short of naming an alternative, but the action-resource pairing is unambiguous.

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: the phrase "Field number from the last read" hints that a prior read is a prerequisite and that element indices are ephemeral, which is genuinely useful. However, there is no explicit statement of when to prefer this over click, or what to do if the field is already populated.

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