Skip to main content
Glama

list_appointments

Read-onlyIdempotent

List appointments overlapping a time window in the connected business. Use Unix milliseconds and a window of up to 31 days. Filter by status, paymentStatus, assigneeId, locationId, contactId or serviceId when needed. Set completed to true for completed appointments or false for records without a completion timestamp. Filter by noShow to include or exclude recorded no-shows.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_appointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
limitNo
noShowNo
offsetNo
statusNo
completedNo
contactIdNo
serviceIdNo
assigneeIdNo
locationIdNo
paymentStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description nonetheless adds substantive context: a hard 31-day window limit, Unix-millisecond time units, and the non-obvious semantics of completed=true (has completion timestamp) versus false (no timestamp). It omits pagination behavior and the default/max limit of 50, which keeps it from a 5.

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?

Three sentences, front-loaded with the core scope and time constraints before the filter list. Every sentence carries information, though the middle enumeration is a flat list that reads slightly like a schema echo rather than added meaning.

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 12-parameter list tool with no output schema and no schema descriptions, the definition should cover pagination and return shape. It explains the time-window core and two tricky filters well, but says nothing about limit/offset defaults or what a result item contains, leaving real gaps.

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 0%, so the description carries the full parameter burden and only partly discharges it. It clarifies the two required time parameters, and explains completed and noShow meaningfully, but simply enumerates status, paymentStatus, assigneeId, locationId, contactId and serviceId without explaining enum values or ID sources, and never mentions limit or offset at all.

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 definition opens with a specific verb and resource: 'List appointments overlapping a time window in the connected business.' The overlap-window scoping is precise and implicitly separates it from siblings such as list_appointment_changes or list_appointment_payments. It does not, however, explicitly name or contrast with any alternative tool, which keeps it below a 5.

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 constraints are stated ('Use Unix milliseconds and a window of up to 31 days'), and the filter parameters are presented as optional ('when needed'). There is no guidance on when to pick this tool over the appointment-related siblings, no exclusions, and no prerequisites. The reader can infer usage, but the definition does not actively route.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources