Skip to main content
Glama
Kartha-AI

MCP Server for Google Cloud Healthcare API

by Kartha-AI

get_patient_careplans

Retrieve patient care plans by specifying patient ID, status, date range, and category using the MCP Server for Google Cloud Healthcare API. Supports clinical workflows with FHIR-based data.

Instructions

Get care plans for a patient

Input Schema

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

Implementation Reference

  • Core implementation of get_patient_careplans tool. Queries FHIR CarePlan resource filtered by patient ID, status, category, and date range. Formats response using formatResponse helper.
    async getPatientCarePlans(args: any) {
      const params = new URLSearchParams();
      params.append('patient', `${args.patientId}`);
      if (args.status) params.append('status', args.status);
      if (args.category) params.append('category', args.category);
      if (args.dateFrom) params.append('date', `ge${args.dateFrom}`);
      if (args.dateTo) params.append('date', `le${args.dateTo}`);
    
      const response = await this.client.get(`/CarePlan?${params}`);
      return this.formatResponse(`fhir://Patient/${args.patientId}/careplans`, response.data);
    }
  • Tool definition including name, description, and input schema validation for get_patient_careplans.
      name: "get_patient_careplans",
      description: "Get care plans for a patient",
      inputSchema: {
        type: "object",
        properties: {
          patientId: { type: "string" },
          status: {
            type: "string",
            enum: ["draft", "active", "suspended", "completed", "cancelled"]
          },
          category: { type: "string" },
          dateFrom: { type: "string", description: "YYYY-MM-DD" },
          dateTo: { type: "string", description: "YYYY-MM-DD" }
        },
        required: ["patientId"]
      }
    },
  • ToolHandler switch case that registers and dispatches the get_patient_careplans tool call to the FhirClient implementation.
    case "get_patient_careplans":
      return await this.fhirClient.getPatientCarePlans(request.params.arguments);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get care plans for a patient', implying a read-only operation, but does not specify permissions required, rate limits, pagination, error handling, or what 'Get' entails (e.g., returns a list or single object). For a tool with 5 parameters and no annotation coverage, this lack of detail is a significant gap, though it does not contradict any annotations.

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?

The description is a single, efficient sentence with zero waste—'Get care plans for a patient' is front-loaded and directly states the action. It avoids redundancy or unnecessary elaboration, making it highly concise and well-structured for its brevity.

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 complexity (5 parameters, 1 required, no output schema, and no annotations), the description is incomplete. It does not address return values (e.g., format, structure), error cases, or behavioral nuances like filtering logic. With schema coverage at 40% and no annotations to fill gaps, the description leaves critical context missing for effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 40% (only 'dateFrom' and 'dateTo' have descriptions), leaving 3 parameters undocumented. The description 'Get care plans for a patient' adds minimal semantic value—it hints at 'patientId' as a key input but does not explain 'category', 'status', or the date parameters beyond what the schema provides. With low coverage, the description fails to compensate adequately, resulting in poor parameter understanding.

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 care plans for a patient' clearly states the verb ('Get') and resource ('care plans for a patient'), making the purpose understandable. However, it lacks specificity about what 'care plans' entail (e.g., treatment plans, goals) and does not differentiate from sibling tools like 'get_patient_conditions' or 'get_patient_procedures', which might overlap in healthcare contexts. This vagueness prevents a higher score.

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 does not mention prerequisites (e.g., needing a valid patient ID), exclusions, or comparisons to sibling tools like 'get_patient_encounters' or 'get_patient_observations'. Without such context, an agent must infer usage from the tool name alone, which is insufficient for optimal selection.

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