Skip to main content
Glama
Sign In
LibreLink MCP Server

LibreLink MCP Server

by amansk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_glucose_stats

Calculate comprehensive glucose statistics over a custom period, including average glucose, GMI, time-in-range, and variability, to identify trends and improve diabetes management.

Instructions

Calculate comprehensive glucose statistics including average glucose, GMI (estimated A1C), time-in-range percentages, and variability metrics. Essential for diabetes management insights and identifying areas for improvement.

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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to analyze (1-90). Default: 7. Common periods: 7 (weekly report), 14 (two weeks), 30 (monthly), 90 (quarterly)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the calculation nature but doesn't mention any potential caveats, preconditions (e.g., connection), output format, or error handling. The description adds no behavioral context beyond the obvious read-only calculation.

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?

Two concise sentences, first is a clear action statement, second adds context. No filler, front-loaded with the verb.

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

Completeness3/5

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

The tool has one optional param, no output schema, no annotations. The description lists the metrics computed, but misses any note on output structure or preconditions. It's adequate for a simple stats tool but leaves some gaps.

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 schema fully describes the days parameter with default and range. The description doesn't mention parameters but that's unnecessary given 100% coverage. Baseline 3 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 the tool calculates glucose statistics with specific metrics (average, GMI, TIR, variability). It distinguishes from sibling tools 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 says it's 'essential for diabetes management insights' but doesn't explicitly contrast with sibling tools or state when to use it instead of history/trends. Usage is implied by the nature of the tool, but no direct alternatives are mentioned.

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