Skip to main content
Glama
Kartha-AI

MCP Server for Google Cloud Healthcare API

by Kartha-AI

get_vital_signs

Retrieve a patient's vital signs history within a specified timeframe using FHIR API, enabling efficient clinical data access and analysis in Google Cloud Healthcare.

Instructions

Get patient's vital signs history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patientIdYes
timeframeNoe.g., 3m, 6m, 1y, all

Implementation Reference

  • The function that implements the core logic for retrieving the patient's vital signs from the FHIR Observation resource using patient ID and optional date range.
    async getPatientVitalSigns(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(`/Observation?${params}`);
      return this.formatResponse(`fhir://Patient/${args.patientId}/vital-signs`, response.data);
    }
  • The switch case statement that dispatches calls to the 'get_vital_signs' tool to the appropriate handler method in FhirClient.
    case "get_vital_signs":
      return await this.fhirClient.getPatientVitalSigns(request.params.arguments);
  • The JSON schema definition for the 'get_vital_signs' tool, including input parameters patientId (required) and timeframe (optional).
    {
      name: "get_vital_signs",
      description: "Get patient's vital signs history",
      inputSchema: {
        type: "object",
        properties: {
          patientId: { type: "string" },
          timeframe: { 
            type: "string",
            description: "e.g., 3m, 6m, 1y, all"
          }
        },
        required: ["patientId"]
      }
    },
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 the tool retrieves history, implying a read-only operation, but doesn't specify whether it requires authentication, has rate limits, returns paginated results, or handles errors. For a tool with no annotations, this leaves critical behavioral traits undocumented.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly. This exemplifies optimal conciseness for a simple tool.

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's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values (e.g., format, data structure), error handling, or operational constraints. Without annotations or an output schema, the description should provide more context to ensure the agent can use the tool effectively.

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 50% (only 'timeframe' has a description), so the description must compensate. It mentions 'patient's vital signs history', which clarifies the 'patientId' parameter's purpose but adds no details beyond what the schema implies. The description doesn't explain parameter formats or constraints, resulting in marginal value over the schema.

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 clearly states the action ('Get') and resource ('patient's vital signs history'), which is specific and unambiguous. It distinguishes this tool from siblings like get_patient_observations or get_patient_conditions by focusing on vital signs, though it doesn't explicitly contrast them. The purpose is well-defined but lacks explicit sibling differentiation.

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 (e.g., needing a valid patient ID), exclusions, or comparisons to similar tools like get_patient_observations. Without such context, the 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