Skip to main content
Glama

phi-longevity-prism

by io.github.Philongevity

Get PRISM methodology

get_methodology
Read-onlyIdempotent

Summarize how the Phi Score works (5 clinical pillars + weights) and link to the full methodology.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesDecision-support disclaimer and synthetic-data rule.
sourceYesAttribution.
phi_scoreYesPlain-English summary of how the 0-100 Phi Score is computed.
agent_docs_urlYesAgent integration docs.
methodology_urlYesFull public methodology page.

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint true, destructiveHint false, covering safety and idempotency. Description adds summarization and linking behavior but not additional traits beyond 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?

Single sentence with front-loaded action ('Summarize...'), no wasted words, highly efficient.

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?

Complete for a simple summary tool: no parameters, output schema exists (documenting return), annotations cover safety. Description adds value by specifying summary content and link.

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?

No parameters (0), schema coverage 100%. Description does not need to explain parameters; baseline score 4 applies.

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?

Description clearly states it summarizes the Phi Score methodology with 5 pillars and weights, plus links to full methodology. Distinct from siblings: analyze_biomarkers (biomarker analysis), full_prism_report (full report), list_supported_biomarkers (listing biomarkers).

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?

Implied usage: quick overview or entry point to methodology. Does not explicitly state when to avoid or alternatives, but sibling tool names provide context for differentiation.

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