Freestyle Libre MCP Server

Get Glucose Summary

get_glucose_summary

Summarize the past 24 hours of glucose data into key metrics: time-in-range, average, highs, lows, and standard deviation. Optionally set custom low and high thresholds for personalized reports.

Instructions

Summarise glucose trends over the past 24 hours: time-in-range, average, highs, lows, and standard deviation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_glucose_summary"
  }
}

Input Schema

Name	Required	Description
`patient_id`	No	Patient ID (auto-selects first connection if omitted)
`low_threshold`	No	Low glucose threshold in mg/dL (default: 70)
`high_threshold`	No	High glucose threshold in mg/dL (default: 180)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It communicates the 24-hour window and the output metrics, which are useful, but it does not explicitly state that it is read-only or mention any permissions or side effect expectations. Non-destructive nature is implied but not stated.

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 that efficiently lists the key output metrics and the time span. Every word contributes, with no filler or repetition.

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?

The tool is simple (3 optional parameters, no output schema), and the description fully explains the purpose, time window, and the expected return values (the listed metrics). This is sufficient for an agent to invoke 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?

The input schema covers all parameters with high detail (patient_id, low_threshold, high_threshold, including defaults). The description adds no parameter-specific context beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 explicitly states the tool summarizes glucose trends over the past 24 hours, listing specific metrics (time-in-range, average, highs, lows, standard deviation). This clearly distinguishes it from siblings like get_current_glucose (single reading) and get_glucose_history (raw data).

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 the tool is for obtaining an aggregate summary rather than raw data, but it does not explicitly mention when to use it vs alternatives. No direct exclusions or alternative tool references are given, so it relies on implicit inference.

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

Deploy Server