Skip to main content
Glama
osjayaprakash

freestyle-libre-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LANGFUSE_BASE_URLNoLangfuse URL for self-hosted or regional instances (default: Langfuse Cloud)
LIBRELINKUP_EMAILYesFollower account email
LIBRELINKUP_REGIONNoOne of US, EU, EU2, AE, AP, AU, CA, DE, FR, JP, LA, RUUS
LANGFUSE_PUBLIC_KEYNoLangfuse public key. Tracing is on only when both public and secret keys are set.
LANGFUSE_SECRET_KEYNoLangfuse secret key. Tracing is on only when both public and secret keys are set.
LIBRELINKUP_PASSWORDYesFollower account password
LANGFUSE_CAPTURE_DATANoSet to 'true' to include tool inputs, outputs and error messages. Default 'false'.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_patientsA

List the people this LibreLinkUp account follows.

get_current_glucoseA

Most recent glucose reading with its trend arrow.

Check age_minutes: if the sensor or phone is out of range, this can be an old reading.

get_glucose_graphA

Glucose readings from roughly the last 12 hours (about every 15 minutes), oldest first.

get_glucose_logbookA

Logged glucose events (scans, alarms) from roughly the last 2 weeks, oldest first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

The four tools target distinct data types: patient list, current reading, 12-hour graph, and 2-week logbook events. Descriptions make boundaries clear, so misselection is unlikely.

Naming Consistency5/5

All names use consistent snake_case with a clear verb_noun pattern (list_patients, get_*). The convention is predictable throughout.

Tool Count5/5

Four tools is well within the ideal 3–15 range and each tool covers a distinct, necessary part of the LibreLinkUp data surface without bloat.

Completeness4/5

Core read workflows are covered (patients, current, recent graph, recent logbook). Minor gaps exist for custom time ranges or deeper historical queries beyond the fixed 12-hour/2-week windows, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues