Skip to main content
Glama

Log treating a low

log_hypo_treatment
Idempotent

Log what the user took to treat a low (e.g. 'juice'), with carbs if they say so.

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

Input Schema

NameRequiredDescriptionDefault
timeNoWhen it happened, in the user's local time: 'HH:MM' (today), 'YYYY-MM-DDTHH:MM', or ISO 8601 with offset. Omit it for right now. Never in the future.
carbs_gNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare it is a non-read, non-destructive, idempotent, closed-world write, so safety is covered. The description adds one useful behavioral rule – include carbs only 'if they say so', i.e. do not infer or fabricate carb amounts – but says nothing about what logging produces or how it affects downstream stats/entries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the example and the conditional carbs clause both earn their place. It is lean to the point of leaving the parameter mapping implicit.

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?

For a 3-parameter, zero-required write tool with no output schema, the definition covers the core intent and the carbs condition. It leaves gaps on which field holds the item text and on what the operation affects downstream, which matter given the low schema coverage.

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?

Schema coverage is only 33%: time is fully documented in-schema but carbs_g and description are not. The description partially compensates by clarifying that carbs_g is conditional on the user stating them and that the free-text item ('juice') is the payload, but it never ties this explicitly to the 'description' field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: logging a treatment for a low, with a concrete example ('juice'). It is separable from siblings like log_glucose or log_meal by the 'treating a low' framing, though it never names an alternative to distinguish itself explicitly.

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?

Usage is implied by 'treating a low' – log this when the user reports consuming something to correct a low. There is no explicit when-not guidance and no pointer to log_meal for ordinary food intake, which is the most likely confusion given the sibling set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.