Anpheros FHIR

Most tools target distinct actions (create, read, search, validate, list, reset). The get_patient_* family (context, summary, timeline, provenance) and list_patients vs search_fhir on Patient are the only mild overlaps, and the descriptions explicitly clarify boundaries (e.g. 'to filter use search_fhir on Patient'). create_patient vs create_fhir_resource is a minor convenience overlap but reasonably distinct.

Almost all names follow a consistent verb_noun snake_case pattern (create_fhir_resource, read_fhir_resource, get_patient_context, search_fhir, validate_fhir_resource). The only deviation is the noun-only sandbox_status, a small inconsistency that doesn't impede readability.

14 tools is well within the sweet spot for a FHIR sandbox server. Each tool covers a distinct capability (validation, creation, reading, search, import, context building, provenance, sandbox administration) and none feels redundant or padding.

Create, read, search, validate, import and context-building are all covered, but there is no update or delete operation for existing FHIR resources, which is a notable gap for a record-manipulation surface. Import and validation mitigate this partially, but agents cannot modify or remove records after creation.