phi-longevity-prism

Analyze biomarkers (synthetic)

analyze_biomarkers

Read-onlyIdempotent

Analyze a SYNTHETIC biomarker panel with Phi Longevity's PRISM engine. Returns tiered, guideline-cited recommendations. For research/education with SYNTHETIC or de-identified data only. Do NOT submit protected health information (PHI). This endpoint is stateless and does not store inputs.

Input Schema

TableJSON Schema

Name	Required	Description
`age`	No	Age in years of the synthetic persona (improves reference-range interpretation).
`biomarkers`	Yes	Map of biomarker name -> numeric value, e.g. { "Hemoglobin A1c": 5.4 }. SYNTHETIC ONLY.
`biologicalSex`	No	Biological sex of the synthetic persona (sex-specific reference ranges).
`conditionFocus`	No	Optional condition track. Default general_wellness.

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Engine metadata for this analysis run.
`issues`	No	Flagged issues detected in the panel.
`claim_panel`	No	Not used on this surface.
`full_report`	Yes	How the agent's owner can get a complete PRISM report.
`recommendations`	Yes	Tiered, guideline-cited recommendations from the PRISM engine.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 26, 2026

removedInput schema / properties / include_partner_options

Removed value: -{
-  "description": "If true, include partner/product options. Default false.",
-  "type": "boolean"
-}

changedOutput schema / properties / claim_panel / description

Previous value: -"OPTIONAL owner handoff: attach these exact values to the owner's Phi Longevity account (sign-in + explicit confirm). Present only when the consent bridge is enabled."New value: +"Not used on this surface."

changedOutput schema / properties / claim_panel / properties / claim_url / description

Previous value: -"One-click claim link — share ONLY with your owner."New value: +"Not used on this surface."

changedOutput schema / properties / full_report / properties / for_your_owner / description

Previous value: -"ACTION: surface get_full_report_url to the person you are helping."New value: +"Plain-language note about the free Phi Longevity account."

Changed5 schema fields changedSep 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / biomarkers / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / required

Previous value: -[
-  "full_report"
-]New value: +[
+  "recommendations",
+  "full_report"
+]

Changed2 schema fields changedAug 23, 2026

addedOutput schema / properties / full_report / properties / for_your_owner

Added value: +{
+  "description": "ACTION: surface get_full_report_url to the person you are helping.",
+  "type": "string"
+}

changedOutput schema / properties / full_report / required

Previous value: -[
-  "what_a_full_report_adds",
-  "get_full_report_url",
-  "agent_docs_url",
-  "data_rule"
-]New value: +[
+  "for_your_owner",
+  "what_a_full_report_adds",
+  "get_full_report_url",
+  "agent_docs_url",
+  "data_rule"
+]

Changed1 schema field changedAug 21, 2026

addedOutput schema / properties / claim_panel

Added value: +{
+  "additionalProperties": false,
+  "description": "OPTIONAL owner handoff: attach these exact values to the owner's Phi Longevity account (sign-in + explicit confirm). Present only when the consent bridge is enabled.",
+  "properties": {
+    "claim_url": {
+      "description": "One-click claim link — share ONLY with your owner.",
+      "type": "string"
+    },
+    "expires_at_ms": {
+      "description": "Epoch ms when the unclaimed panel is hard-deleted.",
+      "type": "number"
+    },
+    "marker_count": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "claim_url",
+    "expires_at_ms",
+    "marker_count",
+    "note"
+  ],
+  "type": "object"
+}

First observedJul 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable beyond-annotation context: the endpoint is stateless and does not store inputs, plus it reiterates the PHI restriction. This meaningfully improves safety transparency.

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 three tight sentences with no filler. The action is front-loaded, followed by scope/safety restrictions and the statelessness note. Every sentence earns its place.

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

Completeness4/5

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

The rich schema, output schema, and annotations cover invocation details, while the description supplies scope, PHI prohibition, and statelessness. The main completeness gap is explicit routing to sibling tools such as quick_check, but the tool remains safely callable as described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters, including age/sex interpretation effects and conditionFocus defaults. The description adds little parameter-level detail beyond restating the synthetic-only constraint, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Analyze') and resource ('SYNTHETIC biomarker panel') and describes the output as 'tiered, guideline-cited recommendations.' It clearly narrows scope to synthetic/de-identified research data, but it does not explicitly distinguish itself from siblings like quick_check or sample_prism_report.

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

Usage Guidelines4/5

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

The description gives clear context: use for research/education with synthetic or de-identified data only, and explicitly forbids submitting PHI. It lacks explicit alternatives or a when-not-to-use comparison with sibling tools, but the constraints are strong enough to guide appropriate selection.

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

All phi-longevity-prism 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.