Skip to main content
Glama
aks129

HealthClawGuardrails

by aks129
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search FHIR Resources

fhir_search
Read-only

Search FHIR resources by patient, code, status, or date, returning paginated, redacted Bundles for safe clinical data access.

Instructions

Search for FHIR resources. Supports FHIR R4 US Core v9 stable resources and FHIR R6 ballot3 experimental resources. Supports patient, code, status, _lastUpdated, _count, _sort parameters. Returns paginated, redacted Bundle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoCode filter — matches code.coding[].code in JSON (e.g., '2339-0' for Glucose)
_sortNoSort order: '_lastUpdated' (asc) or '-_lastUpdated' (desc, default)
_countNoMax results (1-50, capped for token safety)
statusNoStatus filter (e.g., 'final', 'active', 'completed')
patientNoPatient reference filter (e.g., 'Patient/pt-1')
_lastUpdatedNoDate filter with prefix (e.g., 'ge2024-01-01', 'le2024-12-31')
resource_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "Patient",
-  "Encounter",
-  "Observation",
-  "AuditEvent",
-  "Consent",
-  "Permission",
-  "SubscriptionTopic",
-  "Subscription",
-  "NutritionIntake",
-  "NutritionProduct",
-  "DeviceAlert",
-  "DeviceAssociation",
-  "Requirements",
-  "ActorDefinition",
-  "Condition",
-  "Provenance",
-  "AllergyIntolerance",
-  "Immunization",
-  "MedicationRequest",
-  "Medication",
-  "MedicationDispense",
-  "Procedure",
-  "DiagnosticReport",
-  "CarePlan",
-  "CareTeam",
-  "Goal",
-  "DocumentReference",
-  "Location",
-  "Organization",
-  "Practitioner",
-  "PractitionerRole",
-  "RelatedPerson",
-  "Coverage",
-  "ServiceRequest",
-  "Specimen",
-  "FamilyMemberHistory"
-]New value: +[
+  "Patient",
+  "Encounter",
+  "Observation",
+  "AuditEvent",
+  "Consent",
+  "Permission",
+  "SubscriptionTopic",
+  "Subscription",
+  "NutritionIntake",
+  "NutritionProduct",
+  "DeviceAlert",
+  "DeviceAssociation",
+  "Requirements",
+  "ActorDefinition",
+  "Condition",
+  "Provenance",
+  "AllergyIntolerance",
+  "Immunization",
+  "MedicationRequest",
+  "MedicationStatement",
+  "Medication",
+  "MedicationDispense",
+  "Procedure",
+  "DiagnosticReport",
+  "CarePlan",
+  "CareTeam",
+  "Goal",
+  "DocumentReference",
+  "Location",
+  "Organization",
+  "Practitioner",
+  "PractitionerRole",
+  "RelatedPerson",
+  "Coverage",
+  "ServiceRequest",
+  "Specimen",
+  "FamilyMemberHistory"
+]
  2. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it returns a 'paginated, redacted Bundle' and notes that _count is 'capped for token safety', which discloses output behavior and a safety constraint beyond the schema.

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?

Three sentences with no waste. The core purpose is front-loaded, followed by supported versions, parameters, and output behavior. Every sentence earns its place.

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

Completeness4/5

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

For a read-only search tool with rich schema coverage and annotations covering safety, the description is nearly complete. It covers supported FHIR versions, parameters, and output format. It could mention pagination behavior in more detail (e.g., how to request next pages), but the 'paginated' note is sufficient for basic use.

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

Parameters4/5

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

Schema description coverage is 86%, so the schema already documents most parameters. The description adds meaning by grouping the parameters (patient, code, status, _lastUpdated, _count, _sort) and noting the _count cap for token safety, which is not in the schema. It does not fully compensate for the undocumented parameter, but the schema carries most of the burden.

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?

The description states a specific verb ('Search') and resource ('FHIR resources'), and immediately distinguishes itself from siblings like fhir_read and fhir_lastn by listing supported parameters and resource types. It clearly identifies what the tool does and its scope.

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?

The description provides clear context on what the tool supports (FHIR R4 US Core v9 stable and R6 ballot3 experimental resources) and lists the filter parameters, which implies when to use it. However, it does not explicitly state when not to use it or name alternative tools like fhir_read or fhir_lastn for specific use cases.

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

Deploy Server

Other Tools