Skip to main content
Glama
sikcapri

SuperGlookoQuery

by sikcapri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Pod and CGM sensor changes

get_device_events
Read-only

Retrieve pod, infusion-site, and CGM sensor change timestamps to see whether unexplained glucose readings align with recent device changes.

Instructions

Pod or infusion-site changes (a tubeless pump's pod, or a tubed pump's cannula/site, typically changed every few days) and CGM sensor changes, as timestamped events, kept as two separate lists.

DEVICE COVERAGE: whether Glooko reports these events at all depends on the device — confirmed empty (never populated, over a full 30-day check) for a CamAPS FX + Ypso Pump account. Both counts being zero can mean this device combination doesn't report site/sensor changes to Glooko in a way this project can see, not that no changes happened — never assert the latter from an empty result.

These are point-in-time markers, not amounts. They are most useful as CONTEXT for nearby glucose disruption: a fresh pod/site can run high for the first hours while the cannula settles, and a new sensor can read erratically while it warms up. Use them to check whether an unexplained high or a run of odd readings lines up with a recent change. Treat any such link as a possible contributing factor, never assert it as the cause.

Times are plain wall clock time (device-local), not UTC.

Returns: podChanges and sensorChanges arrays of wall-clock timestamps, plus a count for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesRequired. Window end as an ISO 8601 timestamp, e.g. 2026-06-20T00:00:00.000Z — plain wall clock time, same caveat as start (the "Z" is a format artifact, not a UTC claim). Treated as inclusive and must be after start. All timestamps returned by this API are likewise plain wall clock time, unconverted.
startYesRequired. Window start as an ISO 8601 timestamp, e.g. 2026-06-19T00:00:00.000Z. IMPORTANT: despite the trailing "Z", this is plain WALL CLOCK time, not true UTC — Glooko records only the literal date/time the patient's device showed, with no timezone attached. Use the patient's own wall-clock digits directly (no conversion): resolve "yesterday" or "last 3 weeks" straight into the matching wall-clock date and time. Treated as inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description carries the load by disclosing device-dependent population, empty-result ambiguity ('never assert the latter from an empty result'), fixed device-local wall-clock times, and the point-in-time nature of the data. No contradiction with annotations.

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?

The main purpose is front-loaded and paragraphs are logically grouped, but the description runs long and the wall-clock caveat repeats what the schema already states in detail.

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?

With no output schema, it still tells the agent exactly what to expect: podChanges and sensorChanges arrays of wall-clock timestamps plus per-list counts. Together with device coverage and interpretation guidance, an agent has what it needs to call and interpret the tool correctly.

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 both start/end parameters already have thorough wall-clock caveats and inclusiveness rules, so the description needs to add little. It only reinforces the timezone caveat at a general level.

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 opens by naming exactly what the tool returns: 'Pod or infusion-site changes ... and CGM sensor changes, as timestamped events, kept as two separate lists.' This is a specific verb-and-resource statement that clearly separates it from glucose, trend, and chart sibling tools.

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?

It gives a concrete intended use: check whether an unexplained high or odd readings 'lines up with a recent change,' and stresses these are context, never asserted causes. It does not name alternatives or explicit exclusion cases, but the usage context is clear enough for an agent to decide when it applies.

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

Deploy Server

Other Tools