FinchNode Synthetic Health Records

Get synthetic conditions

get_demo_conditions

Read-onlyIdempotent

Use this to get only the conditions of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Diagnoses and problem list, normalized from FHIR R4 Condition. No account or API key. To get conditions 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, idempotentHint, and destructiveHint. The description adds valuable context beyond those: it specifies the synthetic scenario, the source systems, and the absence of authentication requirements. This is helpful without contradicting the annotations.

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?

Two sentences with no redundancy. The first sentence states the purpose and scope; the second gives the alternative and the auth note. Information is front-loaded and every sentence earns its place.

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 0-parameter tool with an output schema and annotations covering safety, the description fully covers what an agent needs: the scenario, the source, the scope, and the alternative for broader queries. Nothing critical 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 0 parameters, and schema coverage is 100% vacuously. The description doesn't need to explain parameters, and the baseline of 4 applies. It adds no parameter-specific info because none is needed.

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?

States a specific verb (get), a specific resource (conditions), and scopes it to the baseline-adult scenario. It explicitly says 'only the conditions' and names the synthetic sources, distinguishing it from sibling tools that retrieve 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?

Explicitly states when to use this tool (to get conditions alone) and when to use the alternative (get_demo_health_record for multiple categories at once). Also notes that no account or API key is required, which is a clear prerequisite.

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?