Skip to main content
Glama

query_health_events

Read-only

Read structured health events for up to 365 dates in an IANA time zone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>",
      "timezone": "<timezone>"
    },
    "name": "query_health_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
cursorNo
timezoneYes
event_typeNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / event_type / enum
      Added value: +[
      +  "activity.exercise",
      +  "biomarker.apob",
      +  "biomarker.blood_pressure",
      +  "biomarker.checkup_report",
      +  "biomarker.comprehensive_panel",
      +  "biomarker.cortisol",
      +  "biomarker.custom",
      +  "biomarker.fasting_insulin",
      +  "biomarker.heart_rate",
      +  "biomarker.hrv",
      +  "biomarker.uric_acid",
      +  "body.face",
      +  "body.skin",
      +  "body.tongue",
      +  "body.weight",
      +  "env.custom",
      +  "env.high_altitude",
      +  "env.long_flight",
      +  "lifestyle.sexual_activity",
      +  "lifestyle.smoking",
      +  "meal.breakfast",
      +  "meal.custom",
      +  "meal.dinner",
      +  "meal.drink",
      +  "meal.lunch",
      +  "meal.snack",
      +  "protocol.custom",
      +  "protocol.hyperbaric",
      +  "protocol.ice_bath",
      +  "protocol.meditation",
      +  "protocol.red_light",
      +  "protocol.sauna",
      +  "sleep.session",
      +  "supp.alcohol",
      +  "supp.caffeine_supplement",
      +  "supp.creatine",
      +  "supp.magnesium",
      +  "supp.medication",
      +  "supp.melatonin",
      +  "supp.nmn",
      +  "supp.omega3",
      +  "supplement.custom",
      +  "symptom.brain_fog",
      +  "symptom.custom",
      +  "symptom.fatigue",
      +  "symptom.high_energy",
      +  "symptom.mood"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint of 'up to 365 dates' and the IANA time zone requirement. However, it does not disclose pagination behavior via the cursor parameter or how event_type filtering affects results.

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 a single front-loaded sentence with no filler. The core purpose and scoping constraints are stated immediately. It is appropriately sized for the amount of information it chooses to convey.

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

Completeness2/5

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

The tool has five parameters, 0% schema description coverage, and a related sibling tool. One sentence covering purpose, date limit, and timezone is not complete enough: it omits cursor pagination, event_type semantics, and explicit differentiation from daily_score. The output schema helps with return values, but the description remains under-specified for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains that timezone should be IANA and implies a date-range limit of 365 dates, but it says nothing about the cursor parameter, event_type filtering, or required from/to semantics. It partially compensates for the coverage gap but leaves key parameters undocumented.

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 and resource: 'Read structured health events.' It also includes meaningful scope constraints (up to 365 dates, IANA time zone). It does not explicitly distinguish the tool from the sibling daily_score, but the resource is clear enough for an agent to identify it as raw event retrieval.

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

Usage Guidelines3/5

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

The description implies usage for reading structured health events rather than aggregated daily scores, but it does not explicitly say when to use this tool versus daily_score or when not to use it. The guidance is present only by implication, with no alternatives or exclusions named.

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