FinchNode Synthetic Health Records

Get synthetic vital signs (vitals)

get_demo_vitals

Read-onlyIdempotent

Use this to get only the vital signs (vitals) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Blood pressure, heart rate, weight, and similar measures, normalized from FHIR R4 Observation. No account or API key. To get vital signs 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 this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond those hints: the data is 'normalized from FHIR R4 Observation' and requires no authentication. This gives the agent a fuller picture of the data provenance and invocation requirements 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?

The description is only two sentences and front-loads the core purpose in the first phrase ('Use this to get only the vital signs'). The alternative tool is named in the same sentence that explains the exclusion condition, and every clause adds useful information 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?

For a zero-parameter, read-only tool with an output schema and comprehensive annotations, this description is complete: it states scope, scenario, data normalization, auth expectations, and the key sibling alternative. Nothing an agent needs to correctly select and call this tool 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 input schema is empty and schema description coverage is 100%, so there are no parameter semantics to explain. The description avoids inventing unnecessary parameter details, which is appropriate for a zero-parameter tool. A 4 reflects that the description need not compensate for any schema gap.

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 names a specific verb and resource ('get only the vital signs (vitals)') and clearly distinguishes itself from sibling category tools by enumerating what counts as vitals: blood pressure, heart rate, weight, and similar measures. It also identifies the target scenario ('baseline-adult') and the source systems, so there is no ambiguity about what this tool returns.

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 states when to use the tool ('only the vital signs') and when not to ('To get vital signs together with other categories, call get_demo_health_record once instead'). It also provides a useful access prerequisite by noting 'No account or API key', which is relevant context for an agent deciding whether this tool is callable in the current environment.

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?