Nova

Upcoming appointments

list_appointments

Read-onlyIdempotent

Retrieve upcoming appointments within a specified number of days, including visit details, who is driving, and location, to help plan care logistics.

Instructions

'When is my doctor appointment?', 'Who's coming this week?' Upcoming visits, who's driving, and where.

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

Input Schema

Name	Required	Description	Default
`days`	No	How far ahead

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results include driver and location, but leaves "upcoming" undefined — the actual time window (default 14 days, max 60) is never mentioned, which is the one behavioral trait an agent most needs here.

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?

Two very short sentences with no filler. It leads with example user phrasings rather than the action itself, which slightly delays the operative statement, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully documented. However, for a tool whose entire behavior hinges on an implicit look-ahead window and whose output overlaps with get_today and care_briefing, the description should say more about scope and how it differs from those siblings.

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 the single parameter 'days' is documented with a default and a 1–60 range, so the schema carries the load. The description adds no meaning about how the window affects results, which is the correct baseline-3 outcome when the schema is complete.

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 makes clear the tool returns upcoming visits along with driver and location, so an agent can tell it lists appointment records rather than alerts or messages. It does not explicitly distinguish itself from adjacent siblings like get_today or care_briefing, which likely surface some of the same schedule information.

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 quoted user questions ("When is my doctor appointment?", "Who's coming this week?") imply the trigger scenarios, but there is no explicit when-to-use statement, no exclusions, and no pointer to alternative tools for other schedule-related questions.

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