Skip to main content
Glama

lookup_health_fact

Read-only

Zero setup — NO key required. Returns ONE already-public federal health fact, list, or tip for a question or topic (e.g. "high blood pressure", "sleep", "type 2 diabetes"), with its federal source (CDC / MedlinePlus / NIH) and a link to the public uphealth.me page. Free + rate-limited. For adaptive, patient-specific message sequencing — receptivity-scored cues + audience-safety verdicts over the full library of federally-sourced facts, lists & tips — get a free Discovery key at https://uphealth.us/signup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesA health question or topic, e.g. "high blood pressure", "sleep", or "type 2 diabetes".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
factYesThe single already-public federal message — a fact, list, or tip (see kind).
topicNoThe matched topic's title.
upgradeYesThe free-key upsell — adaptive sequencing lives behind a Discovery key.
disclaimerYes
attributionYes"Source: <agency> via Uphealth".

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / properties / fact / description
      Previous value: -"The single already-public federal fact."New value: +"The single already-public federal message — a fact, list, or tip (see kind)."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses behavior beyond annotations: returns exactly one item, is rate-limited, and remains public with no key needed. No contradiction with readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is informative but slightly verbose. Front-loaded with key benefits, though could be trimmed without losing clarity.

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 simple lookup tool with one parameter and an output schema, the description fully covers return values (fact, source, link) and usage constraints.

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

Parameters5/5

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

Schema has q with description; description adds concrete examples (e.g., 'high blood pressure') and explains the parameter's purpose, augmenting the schema.

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 returns a single public health fact, list, or tip for a given topic, with source and link. Differentiates from sibling tools like get_next_cued_message which handle adaptive patient-specific messaging.

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?

Explicitly says 'Zero setup — NO key required' for simple lookups, and directs users to get a free key for advanced adaptive messaging. Provides clear when-to-use and alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources