Normalized latest reading: { mg_dl, trend_arrow, timestamp, minutes_ago, has_active_sensor }. Read-only CGM data — not for medical decisions without clinician review.
Bulk support: accepts patient_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| patient_id | No | ||
| patient_ids | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds value by specifying the return fields (mg_dl, trend_arrow, etc.), emphasizing read-only nature, and clarifying medical disclaimer. Contradiction: false.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences in two short paragraphs. Returns fields are listed upfront, followed by bulk support note. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, the description covers purpose, return structure, bulk mode, and a caution. Lacks parameter-level explanations and error handling, but is largely complete for a read-only data retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% with no parameter descriptions. The description only mentions that patient_ids is for bulk support, but fails to explain account, patient_id, or the distinction between single and bulk use. More detail is needed to compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the 'latest reading' with a normalized format listing fields. It is specific but does not differentiate from similar sibling tools like librelink_get_current_glucose, which may serve a similar purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes the tool is read-only and not for medical decisions, and mentions bulk support via patient_ids. However, it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct by function, but librelink_list_accounts and librelink_list_connections are exact aliases, causing confusion. Some glucose tools have overlapping outputs (e.g., librelink_get_current_glucose vs librelink_get_latest_reading), though descriptions help differentiate them.
CGM data tools consistently use the librelink_ prefix, but authentication, connect, marketplace, report_bug, show_version, and toolkit_info lack the prefix, mixing conventions. This inconsistency makes the tool set feel disjointed.
With 16 tools, the set is slightly larger than needed, but it covers the main CGM functionalities plus platform utilities. The number is still reasonable and manageable, with each tool serving a specific purpose.
The CGM data tools provide comprehensive read-only access (current, graph, stats, logbook, etc.), but there are no write operations (e.g., setting targets) or historical data beyond ~12-14 days. The inclusion of marketplace and configuration tools feels out of scope but does not leave critical gaps for the stated domain.