Skip to main content
Glama
Kartha-AI

MCP Server for Google Cloud Healthcare API

by Kartha-AI
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_appointments

Retrieve patient appointments by specifying a patient ID and date range to streamline scheduling and healthcare workflows using Google Cloud Healthcare API.

Instructions

Get patient's Appointments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateFromNoYYYY-MM-DD
dateToNoYYYY-MM-DD
patientIdYes

Implementation Reference

  • src/server/connectors/fhir/FhirClient.ts:227-235 (handler)
    The core handler function that executes the get_appointments tool by querying the FHIR Appointment resource with patient ID and optional date filters.
    async getPatientAppointments(args: any) {
  const params = new URLSearchParams();
  params.append('patient', `${args.patientId}`);
  if (args.dateFrom) params.append('date', `ge${args.dateFrom}`);
  if (args.dateTo) params.append('date', `le${args.dateTo}`);

  const response = await this.client.get(`/Appointment?${params}`);
  return this.formatResponse(`fhir://Patient/${args.patientId}/appointments`, response.data);
}
  • src/server/handlers/ToolHandler.ts:90-91 (handler)
    The switch case in the main tool handler that routes get_appointments calls to the FhirClient implementation.
    case "get_appointments":
  return await this.fhirClient.getPatientAppointments(request.params.arguments);
  • src/server/constants/tools.ts:186-198 (schema)
    The tool definition including name, description, and input schema used for registration and validation.
    {
  name: "get_appointments",
  description: "Get patient's Appointments",
  inputSchema: {
    type: "object",
    properties: {
      patientId: { type: "string" },
      dateFrom: { type: "string", description: "YYYY-MM-DD" },
      dateTo: { type: "string", description: "YYYY-MM-DD" }
    },
    required: ["patientId"]
  }
},
  • src/server/handlers/ToolHandler.ts:37-38 (registration)
    The list tools handler that returns the TOOL_DEFINITIONS array containing the get_appointments tool definition.
    private handleList = async () => ({
  tools: TOOL_DEFINITIONS

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get' which implies a read operation, but doesn't specify if it requires authentication, returns paginated results, includes cancelled appointments, or handles errors. This leaves significant gaps in understanding the tool's behavior beyond basic functionality.

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?

The description is extremely concise with just three words, making it front-loaded and efficient. However, it's arguably too brief, as it could benefit from slightly more context to be fully helpful without becoming verbose.

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

Completeness2/5

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

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover key aspects like return format (e.g., list of appointments with details), error handling, or authentication needs, which are crucial for an AI agent to use this tool effectively in a healthcare 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?

The description mentions 'patient's Appointments' which implies the 'patientId' parameter, but doesn't explain the optional date parameters or their relationship to filtering. With 67% schema description coverage (date parameters described, patientId not), the description adds minimal value beyond what the schema provides, meeting the baseline for moderate coverage.

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

Purpose3/5

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

The description 'Get patient's Appointments' clearly states the verb ('Get') and resource ('patient's Appointments'), making the basic purpose understandable. However, it doesn't differentiate from sibling tools like 'get_patient_encounters' or specify what type of appointments (e.g., medical, scheduled visits), leaving it somewhat vague in context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing a patient ID), exclusions, or how it differs from similar tools like 'get_patient_encounters', leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kartha-AI/google-cloud-healthcare-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server