FinchNode Synthetic Health Records

Get synthetic allergies

get_demo_allergies

Read-onlyIdempotent

Use this to get only the allergies of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Allergies and intolerances, normalized from FHIR R4 AllergyIntolerance. No account or API key. To get allergies 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.5/5.0

Behavior3/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 that it returns normalized data from FHIR R4 AllergyIntolerance and that it's synthetic, which is useful. However, it doesn't describe the output structure or whether the data is paginated, but the output schema exists to cover 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 compact and front-loaded with the key purpose. It names the scenario, the data source, the auth requirement, and the alternative in two sentences without waste.

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 parameterless read-only tool with an output schema and annotations covering safety, the description is complete. It tells the agent exactly what data it will get, that it's synthetic, and how to get a broader record if needed.

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 0 parameters, so there are no parameter semantics to document. The description still explains the fixed scope (baseline-adult scenario) and data source, which is more than necessary for a parameterless tool.

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 allergies for baseline-adult, one of FinchNode's 12 synthetic scenarios, and specifies the data source (FHIR R4 AllergyIntolerance). It distinguishes itself from sibling tools by noting it returns only allergies, not other categories.

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 says when to use this tool (to get only allergies) and when to use an alternative (get_demo_health_record to get allergies with other categories). It also notes no account or API key is needed, which is useful context.

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?