Skip to main content
Glama

acuity_scheduling_status

Verify your Cotlet.dev account, available credits, and Acuity Scheduling connection are ready before running scheduling actions.

Instructions

Check that your Cotlet.dev account and Acuity Scheduling are ready: account, credits and Acuity Scheduling connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, but the tool is a zero-parameter read-only diagnostic, so the risk surface is inherently low and the description does disclose the three things being verified. It does not say what a result looks like (per-check booleans vs. error text), whether it performs a live network call, or what auth it needs.

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 sentence with the verb and the checked items front-loaded, and no filler. The trailing colon list is slightly clunky but functional.

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?

There is no output schema and no annotations, so the description carries the burden of describing the return value for a diagnostic tool — and it does not. An agent knows what is checked but not how to interpret a success, partial failure, or missing-credentials response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the colon-separated list of checks is a small bonus but adds no parameter meaning.

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 a specific action (check readiness) and enumerates the resources inspected: the Cotlet.dev account, credits, and the Acuity Scheduling connection. That distinguishes it from the action-oriented siblings (open, click, read, type), though it never explicitly frames itself as a pre-flight check relative to them.

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 'ready' hints that this is a prerequisite check run before other Acuity tools, but the guidance is only implied. There is no explicit statement of when to call it, when not to, or what to do if the check fails.

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