Skip to main content
Glama

phi-longevity-prism

by io.github.Philongevity

Quick biomarker range check (instant, no analysis)

quick_check
Read-onlyIdempotent

FASTEST first call: instantly flag a few biomarker values against PRISM's longevity-optimized reference ranges (local, no engine round-trip). Ideal for "what does my mean?". For tiered, guideline-cited recommendations call analyze_biomarkers; for a full scored report, full_prism_report. 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
NameRequiredDescriptionDefault
biomarkersYesMap of biomarker name -> value, e.g. {"HbA1c":6.1,"LDL-C":145}. SYNTHETIC ONLY.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesScope disclaimer — quick flags, not a diagnosis or full analysis.
flagsYesRange flags for each recognized biomarker.
unmatchedNoSubmitted names not in the 51-marker catalog.
claim_panelNoOPTIONAL owner handoff (present only when the consent bridge is enabled).
full_reportYesHow the agent's owner can get a complete PRISM report.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed1 schema field changed
    • 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"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it readOnly, idempotent, and non-destructive. The description adds useful behavioral context beyond that: it is stateless, does not store inputs, runs locally, and does not trigger an engine round-trip. This substantially clarifies the operational behavior 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 compact, front-loaded with the core purpose, and every sentence earns it keep-placement by adding routing, constraints, or behavioral context. 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?

Given the single parameter, rich annotations, and existing output schema, the description covers what an agent needs: when to call it, what it does, which siblings to use instead, and the data-handling constraints. Nothing critical is missing.

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 coverage is 100% for the only parameter ('biomarkers'), so the schema already documents the required map-of-name-to-value shape. The description reinforces that values should be SYNTHETIC and limited to 'a few biomarker values', but it doesn't add materially new parameter semantics.

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 states a specific action and resource: 'instantly flag a few biomarker values against PRISM's longevity-optimized reference ranges.' It also differentiates itself from siblings by emphasizing 'local, no engine round-trip' and being the 'FASTEST first call'.

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?

Usage is explicit: use for quick 'what does my value mean?' checks, not for tiered recommendations or full reports. It names the alternatives ('analyze_biomarkers' and 'full_prism_report') and states strict constraints: SYNTHETIC/de-identified data only and no PHI.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools are clearly distinct: reference/methodology functions, a fixed sample, a quick local check, and the paid full report. analyze_biomarkers and full_prism_report overlap, but the descriptions explicitly differentiate the free tiered recommendations from the paid multi-track report.

Naming Consistency3/5

analyze_biomarkers, get_methodology, and list_supported_biomarkers follow a clear verb_noun pattern, but quick_check and full_prism_report are noun-phrase style, and sample_prism_report is ambiguous between noun and verb. The names are readable but the convention is mixed.

Tool Count5/5

Six tools is a well-scoped size for this server's purpose: reference data, methodology, quick screening, full analysis, paid report, and a sample output. Each tool earns its place without redundancy or bloat.

Completeness5/5

The tool surface covers the full user journey: learn about biomarkers, understand methodology, preview a sample report, run a quick check, get detailed recommendations, and purchase the full report. No obvious dead ends or critical missing operations for the stated PRISM domain.

Resources