Skip to main content
Glama
lozit

mcp-freestyle

by lozit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LIBRELINKUP_EMAILYesYour LibreLinkUp follower account email (not the primary LibreLink one).
LIBRELINKUP_PRODUCTNoProduct identifier for the LibreLinkUp client.llu.android
LIBRELINKUP_VERSIONNoPinned client version. Upstream rejects stale values — if requests start failing, set this to the current LibreLinkUp app version.4.16.0
LIBRELINKUP_BASE_URLNoEntry point URL for the LibreLinkUp API; the regional host is discovered at login.https://api.libreview.io
LIBRELINKUP_PASSWORDNoPassword for the LibreLinkUp follower account. Overrides the OS keychain. For CI or one-off runs.keychain

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_current_glucoseA

Read the most recent glucose measurement from the FreeStyle sensor, with the instant it was actually measured. The value is the latest one upstream holds, not a live reading — always report measured_at rather than calling it 'now'. Informational only: this is not a medical device and must not be used for any treatment decision.

get_glucose_historyA

Glucose readings over the last N hours (max 12), with time-in-range computed against the account's own target band. Upstream holds only about 12 hours of detailed data and ignores any longer request, so the response always states the range it actually covered and sets truncated when that is less than asked — report that range, never the one requested. Collection gaps are listed separately and are not interpolated across; a percentage over a series with gaps describes only the covered time. Informational only: not a medical device, and not a basis for any treatment decision. This is not an HbA1c or GMI estimate — those need weeks of data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one returns the most recent glucose reading, while the other returns a historical series over a requested time range. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tool names follow the same 'get_' prefix followed by a descriptive noun (current_glucose, glucose_history). The naming pattern is consistent and predictable.

Tool Count3/5

With only two tools, the server feels thin, but the domain is narrow (reading glucose data from a sensor). The two tools cover the essential operations, making the count borderline but not unreasonable.

Completeness4/5

The server provides access to both current and historical glucose data, which covers the core read-only functionality for the domain. Minor gaps exist (e.g., no health/sensor status), but the available tools are sufficient for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources