Loading ToolBench

Reading the current corpus…

fhir4java-agents MCP server · D · ToolBench

fhir4java-agents

github.com/sg-victorchai/fhir4java-agents

Model Context Protocol (MCP) integration for AI-ready FHIR server capabilities. Provides AI agents with tools to discover FHIR server capabilities, manage resources, and query healthcare data.

2026-07-28+STREAMABLE_HTTP1 tools

55/100

Definition Quality65

Protocol Readiness72

Supportability26

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

Single tool (fhir_discover) with moderately detailed schema and description. Naming is acceptable but generic. Parameter descriptions are present with enums for topic selection. Output schema is not documented in the provided code. The tool itself is read-only and low-risk, but the server lacks multiple tools that would demonstrate composition patterns. Error handling and recovery guidance are not visible in the source excerpt.

Tools (1)

fhir_discoverread onlyauthsource verified65/100

Discover FHIR server capabilities including resources, search parameters, and operations

Issues (5)

HIGHtool-response-schema ↗

No output schema documentation. The tool description does not specify what fields are returned, their types, or structure. LLMs cannot plan downstream actions without knowing the response format.

fhir_discover

MEDIUMtool-naming ↗

Generic tool name 'fhir_discover' lacks a clear verb-noun pattern. 'list_fhir_resources', 'get_fhir_capabilities', or 'search_fhir_metadata' would more explicitly signal intent.

fhir_discover

MEDIUMparameter-description ↗

Parameter 'resourceType' description is sparse: 'Optional: Filter by resource type'. Does not explain format (e.g., 'FHIR resource type like Patient, Observation'), valid examples, or how filtering works across different topic values.

fhir_discover

MEDIUMrecovery-guide ↗

No error handling or recovery guidance visible. Tool description does not explain failure modes (e.g., invalid FHIR version, unreachable server) or what the agent should do if discovery fails.

fhir_discover

Recommendations

Add output schema documentation to fhir_discover. Document: { resources: [{name, description, operations}], searchParams: {[resourceType]: [{name, type, documentation}]}, operations: [{name, url, description, params}], capabilities: {supported_versions, publish_endpoints, subscription_formats} }. Include example values.
Rename tool to be more explicit: 'list_fhir_capabilities', 'get_fhir_structure', or 'search_fhir_metadata' depending on primary use case.
Enhance resourceType parameter: 'Optional FHIR resource type (e.g., Patient, Observation, Condition) to filter results. If omitted, returns all available types for the specified topic.'
Add error handling section to description: 'Returns structured error with code (INVALID_VERSION, SERVER_UNREACHABLE, UNSUPPORTED_TOPIC) and guidance. If FHIR version unsupported, recommends R4B or R5.'
Implement additional tools to complete the agent toolkit: search_fhir_resources (query with parameters), get_fhir_resource (fetch by ID), validate_fhir_resource (profile validation), create_fhir_resource (POST with validation), update_fhir_resource (PATCH/PUT).
Add parameter constraints: fhirVersion enum already present (R5, R4B), good. Topic enum present, good. Add minLength/maxLength or pattern to resourceType if it has format rules (e.g., PascalCase).
Document rate limits, pagination, and result caps in the tool description if applicable.

Score history

Overall score trend

↑ 30 points across a rubric change (v1 → v2)

55/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	D	55	2026-07-28+	v2
2026-03-09	F	25	-	v1