Skip to main content
Glama

insync_list_appointments

Read-only

List a patient's upcoming or past appointments with date, time, provider, facility, visit type, status and expected copay.

Instructions

List the patient’s appointments / visits — upcoming or past — with date, time, provider, facility, visit type, status and expected copay. Covers therapy, psychiatry and any other scheduled visit.

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": "insync_list_appointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default 1.
viewNocompact (default) projects each record to the fields a caller acts on; "full" keeps every field this server understands; "raw" returns the portal payload untouched; "brief" returns one line per visit: <type> with <provider> at <facility> — <ISO start> — <status>.
whenNoWhich appointments to list. Default upcoming.upcoming
page_sizeNoAppointments per page (1–100). Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands; \"raw\" returns the upstream payload unprojected. compact projects each record to the fields a caller acts on; \"full\" keeps every field this server understands; \"raw\" returns the portal payload untouched."New value: +"compact (default) projects each record to the fields a caller acts on; \"full\" keeps every field this server understands; \"raw\" returns the portal payload untouched; \"brief\" returns one line per visit: <type> with <provider> at <facility> — <ISO start> — <status>."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full",
      -  "raw"
      -]New value: +[
      +  "compact",
      +  "full",
      +  "raw",
      +  "brief"
      +]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds useful behavioral context by listing exactly which fields come back and asserting the result set spans all visit categories, but it says nothing about pagination behavior, result ordering, or empty-result handling beyond what the schema states.

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?

Two tight sentences with the core action and scope front-loaded, followed by the returned-field list and the coverage note. No redundant or filler wording.

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?

With no output schema, the description usefully compensates by naming the returned fields and the breadth of visit types. For a read-only list tool with fully documented parameters this is nearly complete; only pagination/ordering expectations are unaddressed.

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 two parameters are enums with documented meanings, so the schema carries the parameter burden. The description only echoes the 'upcoming or past' distinction that the `when` enum already encodes and adds no guidance on `view`, `page`, or `page_size`.

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 gives a specific verb plus resource ('List the patient's appointments / visits') and scopes it to upcoming or past, with the returned fields enumerated. It does not explicitly distinguish itself from the related sibling insync_get_appointment_calendar, so sibling differentiation is left implicit.

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 'upcoming or past' phrasing implies the two usage modes and the coverage note ('therapy, psychiatry and any other scheduled visit') suggests this is the general-purpose listing. However, it never states when to prefer this over insync_get_appointment_calendar, insync_find_appointment_slots, or the calendar sibling, and gives no exclusions.

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