Skip to main content
Glama
Sign In
Freestyle Libre MCP Server

Freestyle Libre MCP Server

by jonnyhaynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Current Glucose Reading

get_current_glucose

Fetch a patient's latest blood glucose reading, returning values in mg/dL and mmol/L plus trend direction.

Instructions

Fetch the latest blood glucose reading for a patient. Returns the glucose value in both mg/dL and mmol/L, plus trend direction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patient_id": "<patient_id>"
    },
    "name": "get_current_glucose"
  }
}

Input Schema

NameRequiredDescriptionDefault
patient_idYesPatient ID from get_connections (or leave blank to auto-select first connection)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

There are no annotations provided, so the description carries the burden. It discloses what is returned (mg/dL, mmol/L, trend direction), which is useful, but does not mention whether the operation is read-only, data freshness, authentication requirements, or potential errors. For a simple fetch this is acceptable, but it could be richer.

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 two concise sentences, front-loaded with the core purpose and key return details, with no wasted words.

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

Completeness4/5

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

Given the tool's simplicity (one parameter, no output schema), the description adequately covers what it does and what it returns. It is slightly limited by not mentioning data freshness or edge cases, but overall it is complete enough for selecting and invoking the tool.

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 already provides complete documentation for the single parameter (patient_id from get_connections or leave blank). The description adds no additional meaning about parameters, so it meets the baseline without exceeding it.

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 clearly states the action ('Fetch') and the resource ('latest blood glucose reading'), and distinguishes it from sibling tools like glucose history and summary by specifying it returns the current reading with value and trend direction.

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?

The context is clear: use this tool to get the most recent glucose reading. However, it does not explicitly compare with alternatives like get_glucose_history or get_glucose_summary, so it lacks explicit when-to-use vs. when-not-to-use guidance.

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