phi-longevity-prism

Quick biomarker range check (instant, no analysis)

quick_check

Read-onlyIdempotent

Instantly flags a few biomarker values against PRISM's longevity-optimized reference ranges (local check, no engine call). 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	Default
`biomarkers`	Yes	Map of biomarker name -> value, e.g. {"HbA1c":6.1,"LDL-C":145}. SYNTHETIC ONLY.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	Scope disclaimer — quick flags, not a diagnosis or full analysis.
`flags`	Yes	Range flags for each recognized biomarker.
`unmatched`	No	Submitted names not in the 51-marker catalog.
`claim_panel`	No	Not used on this surface.
`full_report`	Yes	How the agent's owner can get a complete PRISM report.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 26, 2026

changedOutput schema / properties / claim_panel / description

Previous value: -"OPTIONAL owner handoff (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."

Changed4 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"

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "claim_panel": {
+      "additionalProperties": false,
+      "description": "OPTIONAL owner handoff (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"
+    },
+    "flags": {
+      "description": "Range flags for each recognized biomarker.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "description": "Biomarker name as PRISM recognizes it.",
+            "type": "string"
+          },
+          "pillar": {
+            "description": "Clinical pillar.",
+            "type": "string"
+          },
+          "status": {
+            "description": "One of: within / above / below longevity-optimized range.",
+            "type": "string"
+          },
+          "unit": {
+            "description": "Measurement unit.",
+            "type": "string"
+          },
+          "value": {
+            "description": "The submitted value.",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "value",
+          "unit",
+          "pillar",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "full_report": {
+      "additionalProperties": false,
+      "description": "How the agent's owner can get a complete PRISM report.",
+      "properties": {
+        "agent_docs_url": {
+          "type": "string"
+        },
+        "data_rule": {
+          "type": "string"
+        },
+        "get_full_report_url": {
+          "description": "Signup link (free account) for the agent's owner.",
+          "type": "string"
+        },
+        "what_a_full_report_adds": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "what_a_full_report_adds",
+        "get_full_report_url",
+        "agent_docs_url",
+        "data_rule"
+      ],
+      "type": "object"
+    },
+    "note": {
+      "description": "Scope disclaimer — quick flags, not a diagnosis or full analysis.",
+      "type": "string"
+    },
+    "unmatched": {
+      "description": "Submitted names not in the 51-marker catalog.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "flags",
+    "note",
+    "full_report"
+  ],
+  "type": "object"
+}

AddedAug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable behavioral context beyond those hints: the check is local, makes no engine call, is stateless, and does not store inputs. This meaningfully informs the agent about side effects and data handling.

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: the first sentence states the operation and scope, the second adds data-class restrictions, and the third clarifies statelessness. Every sentence earns its place and there is no redundant filler.

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?

The tool has one simple parameter, an output schema, and rich annotations, so the description does not need to explain return values. It covers the essential additional context an agent needs: intended use, data sensitivity, PHI prohibition, and stateless behavior. It is complete for correct invocation.

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%, and the schema already explains the biomarker map format and gives an example. The tool description adds no parameter-specific meaning beyond restating that biomarker values are checked, so the baseline of 3 is appropriate.

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 uses a specific verb ('flags') and a specific resource ('biomarker values against PRISM's longevity-optimized reference ranges'), and it distinguishes itself from a heavier sibling like analyze_biomarkers by noting it is a local check with no engine call. The title reinforces this by adding 'instant, no analysis'.

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 clearly scopes when this tool is appropriate: research/education only, with synthetic or de-identified data, and never with PHI. It does not explicitly name alternatives for other use cases, but the 'no engine call' distinction and the data restrictions give an agent clear enough context to choose it for quick local checks.

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.