clinic-mcp-server

Overview Schema Source Related Servers Discussions Admin

List appointments

list_appointments

Read-only

Retrieve confirmed appointments within a given date range. Returns an empty list if none exist, distinguishing from errors.

Instructions

List confirmed appointments between date_from and date_to (inclusive).

date_to must be on or after date_from. Empty list with status=ok means no
confirmed appointments in that window — distinct from a database failure,
which raises a tool error.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "list_appointments"
  }
}

Input Schema

Name	Required	Description	Default
`date_to`	Yes	Inclusive range end (YYYY-MM-DD), clinic local calendar.
`date_from`	Yes	Inclusive range start (YYYY-MM-DD), clinic local calendar.

Output Schema

Name	Required	Default
`count`	Yes
`status`	No	ok
`date_to`	Yes
`date_from`	Yes
`appointments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate a read-only, non-destructive tool. The description adds behavioral insight by clarifying that an empty list is distinct from a database error, which helps the agent interpret results correctly.

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 front-load the core purpose and critical constraint. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description adequately covers the behavior for edge cases (empty vs error). Parameter definitions are fully covered in the schema, and sibling tools are provided for context.

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% with descriptions for both parameters (inclusive range, clinic calendar). The description adds the constraint that date_to must be on or after date_from, but this is a minor addition beyond the schema definitions.

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 the tool lists confirmed appointments within a date range, with inclusive boundaries. Distinguishes from siblings like search_clinic_docs and get_patient_record by focusing on appointment listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes the scenario for use (listing confirmed appointments by date) and specifies that an empty list with status=ok indicates no appointments. However, it does not mention when not to use this tool or provide explicit alternatives.

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

Deploy Server