Skip to main content
Glama
rkirkendall

Medplum MCP Server

by rkirkendall

getEncounterById

Retrieve specific healthcare encounter details by providing its unique ID, enabling efficient access to patient interaction records within the Medplum FHIR server.

Instructions

Retrieves an encounter by its unique ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
encounterIdYesThe unique ID of the encounter to retrieve.

Implementation Reference

  • The core handler function that authenticates with Medplum, validates the encounter ID, reads the Encounter FHIR resource by ID, returns it or null if not found, handling not-found errors gracefully.
    export async function getEncounterById(args: { encounterId: string }): Promise<Encounter | null> {
      await ensureAuthenticated();
      if (!args.encounterId) {
        throw new Error('Encounter ID is required to fetch an encounter.');
      }
      try {
        const encounter = await medplum.readResource('Encounter', args.encounterId);
        return encounter;
      } catch (error: any) {
        if (error.outcome?.issue?.[0]?.code === 'not-found') {
          return null;
        }
        throw error;
      }
    }
  • JSON Schema definition for the input parameters of the getEncounterById tool, specifying the required 'encounterId' string parameter.
      name: 'getEncounterById',
      description: 'Retrieves a specific encounter resource by its unique ID.',
      input_schema: {
        type: 'object',
        properties: {
          encounterId: {
            type: 'string',
            description: 'The unique ID of the encounter to retrieve.',
          },
        },
        required: ['encounterId'],
      },
    },
  • MCP-specific inputSchema for the getEncounterById tool used by the server, defining the required 'encounterId' parameter.
    name: "getEncounterById",
    description: "Retrieves an encounter by its unique ID.",
    inputSchema: {
      type: "object",
      properties: {
        encounterId: {
          type: "string",
          description: "The unique ID of the encounter to retrieve.",
        },
      },
      required: ["encounterId"],
    },
  • src/index.ts:32-37 (registration)
    Import statement registering the getEncounterById function from encounterUtils for use in the MCP server.
    import {
      createEncounter,
      getEncounterById,
      updateEncounter,
      searchEncounters,
    } from './tools/encounterUtils.js';
  • src/index.ts:965-965 (registration)
    Entry in the toolMapping object that maps the tool name 'getEncounterById' to its handler function for execution.
    getEncounterById,
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 this is a retrieval operation, implying it's read-only, but doesn't cover other important aspects like error handling (e.g., what happens if the ID doesn't exist), authentication needs, rate limits, or response format, which are critical for safe invocation.

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, clear sentence that efficiently conveys the core purpose without any unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema) and high schema coverage, the description is minimally adequate. However, it lacks details on behavioral aspects like error cases or response structure, which could help the agent use it more effectively, keeping it at a baseline score.

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 schema description coverage is 100%, with the parameter 'encounterId' fully documented in the schema. The description doesn't add any additional meaning or context beyond what's in the schema (e.g., format examples or constraints), so it meets the baseline score of 3 for high schema coverage.

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 ('Retrieves') and resource ('an encounter'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get' tools (like getPatientById, getObservationById) beyond specifying the resource type, which is why it doesn't reach a score of 5.

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 when to choose this over 'searchEncounters' for broader queries or other 'get' tools for different resources, leaving the agent to infer usage from context 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/rkirkendall/medplum-mcp'

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