medicover-mcp

list_appointments

Retrieve a patient's scheduled appointments with details including appointment ID and rescheduling eligibility. Filter by upcoming, past, or all appointments.

Instructions

List a patient's appointments (upcoming by default).

Each appointment includes an opaque appointment_id (pass it to reschedule_appointment) and a can_reschedule flag. Read-only.

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
`state`	No	Which appointments: 'Planned', 'Past', or 'All'.	Planned
`patient_id`	No	MRN of the patient. Defaults to the account holder when omitted.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Declares read-only nature and default date filter, which are key behavioral traits. No annotations exist, so description carries full burden; it does well for a simple list tool but lacks details on authentication or rate limits.

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?

Three succinct sentences covering purpose, output details, and read-only status. No filler or redundancy.

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?

Given output schema exists and complexity is low, description provides necessary context: default upcoming, opaque id, read-only. Lacks pagination/ordering details but still adequate.

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 coverage is 100%, so baseline is 3. Description adds minimal extra meaning beyond schema (e.g., 'upcoming' maps to default state). No significant new information for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'List' and resource 'appointments' with patient scope and default upcoming behavior. Distinguishes from siblings by focusing on patient's existing appointments and mentioning how appointment_id is used with reschedule_appointment.

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?

Implies usage for viewing appointments but does not explicitly state when to use this vs book_appointment or search_slots. No exclusion criteria or alternative guidance provided.

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

Deploy Server