FinchNode Synthetic Health Records

Get synthetic immunizations

get_demo_immunizations

Read-onlyIdempotent

Use this to get only the immunizations of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Vaccination history, normalized from FHIR R4 Immunization. No account or API key. To get immunizations together with other categories, call get_demo_health_record once instead of calling several of these tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`record`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 26, 2026
- removedOutput schema / properties / record / properties / consent / properties / receiptIds / maxItems
```
Removed value: -0
```
- removedOutput schema / properties / record / properties / consent / properties / receiptIds / minItems
```
Removed value: -0
```
- removedOutput schema / properties / record / properties / consent / properties / receipts / maxItems
```
Removed value: -0
```
- removedOutput schema / properties / record / properties / consent / properties / receipts / minItems
```
Removed value: -0
```
- removedOutput schema / properties / record / properties / id / const
```
Removed value: -"patient-demo-001"
```
- addedOutput schema / properties / record / properties / id / enum
```
Added value: +[
+  "patient-demo-001",
+  "patient-demo-polypharmacy",
+  "patient-demo-pediatric-asthma",
+  "patient-demo-multi-source",
+  "patient-demo-sparse",
+  "patient-demo-messy-coding",
+  "patient-demo-rate-limited",
+  "patient-demo-consent-revoked",
+  "patient-demo-consent-partial",
+  "patient-demo-source-unavailable"
+]
```
- removedOutput schema / properties / record / properties / meta / properties / syncStatus / const
```
Removed value: -"simulated"
```
- addedOutput schema / properties / record / properties / meta / properties / syncStatus / enum
```
Added value: +[
+  "simulated",
+  "partial"
+]
```
First observedSep 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context: no account or API key is needed, and the data is normalized from FHIR R4 Immunization. It also clarifies the data source is synthetic. The only minor gap is not describing the output format, but the output schema exists and covers that.

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 two sentences and every clause earns its place. The first sentence states the exact scope and source, and the second sentence provides the routing alternative. It is front-loaded with the most important information (what this tool returns) and wastes no words.

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

Completeness5/5

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

For a zero-parameter, read-only tool with an output schema, the description is complete. It tells the agent what data is returned, from which scenario, from which systems, that no auth is needed, and when to use a sibling instead. There is nothing an agent needs to know to call this tool correctly that is missing.

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?

The tool has zero parameters, so the schema is trivially complete. The description adds context about what the returned data represents (vaccination history normalized from FHIR R4 Immunization) and the scenario scope. With no parameters to document, the description's job is to clarify the data scope, which it does well.

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 clearly states the tool returns immunizations from a specific synthetic scenario (baseline-adult) and names the source systems. It also distinguishes itself from the broader get_demo_health_record tool by explicitly saying it gets 'only' immunizations. The verb 'get' plus the resource 'immunizations' and the scope 'baseline-adult' make the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to use this tool: when only immunizations are needed from the baseline-adult scenario. It also provides a clear alternative: use get_demo_health_record when multiple categories are needed. This is strong usage guidance that prevents the agent from calling several tools unnecessarily.

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

All FinchNode Synthetic Health Records tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?