FinchNode Synthetic Health Records

Get synthetic visits (encounters)

get_demo_encounters

Read-onlyIdempotent

Use this to get only the visits (encounters) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Encounters, appointments, and care teams, normalized from FHIR R4 Encounter, Appointment, CareTeam. No account or API key. To get visits 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 cover read-only, idempotent, and non-destructive behavior. The description adds that no authentication is required ('No account or API key') and clarifies the data is synthetic, which is useful behavioral context beyond the annotations. There is no contradiction.

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 concise yet comprehensive, front-loading the core purpose and then efficiently covering the scenario, data types, authentication, and alternative usage. Every sentence adds value without redundancy.

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?

With no parameters and an existing output schema, the description fully covers what the tool returns, the scenario it applies to, and the conditions for use. It also points to the alternative tool for broader needs, making it complete for an agent to decide when to invoke it.

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?

There are zero parameters, so the description has nothing to add about parameter usage. Per the rubric, 0 params grants a baseline score of 4. The description does not need to compensate for missing schema details.

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 identifies the tool's function: retrieving synthetic encounters (visits) for the 'baseline-adult' scenario, and specifies the included data types (encounters, appointments, care teams) and source systems. It also differentiates from siblings by explicitly noting that for multiple categories, get_demo_health_record should be used instead.

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?

It explicitly states when to use this tool ('get only the visits') and provides a clear alternative for broader data needs ('call get_demo_health_record once instead'). The 'No account or API key' note also clarifies the authentication requirement, which is a usage guideline.

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?