Skip to main content
Glama

insync_get_appointment_calendar

Read-only

Retrieve scheduled visits for a date range, including day, time slot, and label; defaults to the current month when no range is provided.

Instructions

Get the monthly appointment calendar — the day, time slot and label of each scheduled visit in a date range. Defaults to the current month when no range is given.

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

Input Schema

NameRequiredDescriptionDefault
toNoRange end (ISO YYYY-MM-DD). Defaults to the last day of the current month.
fromNoRange start (ISO YYYY-MM-DD). Defaults to the first day of the current month.
viewNoResponse 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / from / format
      Added value: +"date"
    • changedInput schema / properties / from / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / to / format
      Added value: +"date"
    • changedInput schema / properties / to / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  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 and the description only needs to add context. It adds the returned field set and the current-month default, but says nothing about pagination, ordering, timezone handling, or whether cancelled/pending visits are included — meaningful gaps for a scheduling tool.

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 sentences with no repetition or filler, and the core scope (calendar contents) is front-loaded ahead of the default-range note. Every clause carries information.

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 correctly compensates by naming the returned fields (day, time slot, label). All three parameters are self-documented in the schema and there are no required params to explain; only return-volume/ordering details are missing, which is minor for a read-only calendar tool.

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 date parameters and the view enum are already documented in the schema, making 3 the baseline. The description restates the default-month behavior already present in the schema and adds no new meaning for the compact/full/raw view choice.

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?

Specific verb + resource ("Get the monthly appointment calendar") followed by the exact fields returned (day, time slot, label), which tells an agent what shape of data it is asking for. It distinguishes a calendar/visit view from a general records listing, but never names insync_list_appointments, so differentiation from the closest sibling 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 "monthly calendar" framing implies a scheduling/calendar-view use case, and the default range is stated, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as insync_list_appointments or insync_find_appointment_slots. Usage is inferable rather than stated.

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