Skip to main content
Glama
health-os

health-os

record_medication

Add a medication or supplement the user currently takes (stored immediately as approved). medication_name: brand or generic, with the strength if it has one (e.g. "Minoxidil 5%"); start_date: YYYY-MM-DD; dose_amount + dose_unit (e.g.

Instructions

Add a medication or supplement the user currently takes (stored immediately as approved). medication_name: brand or generic, with the strength if it has one (e.g. "Minoxidil 5%"); start_date: YYYY-MM-DD; dose_amount + dose_unit (e.g. 1000 + mg, 1 + ml) and times_per_day — record these whenever known, check_medication_safety uses them (e.g. total daily paracetamol); product_type: prescription (default) / otc / supplement / herbal; prescribed_for: optional reason; atc_code: optional; route: oral / topical / inhaled / injection / … Check get_medications first to avoid duplicates. Never use this to change a prescribed dose — that is for the doctor.

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": {
      "medication_name": "<medication_name>",
      "start_date": "<start_date>"
    },
    "name": "record_medication"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeNo
atc_codeNo
dose_unitNo
start_dateYes
dose_amountNo
product_typeNoprescription
times_per_dayNo
prescribed_forNo
medication_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / route
      Added value: +{
      +  "default": "",
      +  "title": "Route",
      +  "type": "string"
      +}
  2. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a non-destructive, non-idempotent write in a closed world; the description adds genuinely new behavior: records are committed immediately as approved (no staging/approval step, unlike stage_lab_panel), duplicates are possible so a pre-check is needed, and dose fields feed the safety checker. That is real operational context beyond the structured hints.

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?

Purpose and storage behavior are front-loaded, and every clause carries usable information with no filler. It is dense prose rather than a structured list, though, so scanning nine parameter explanations in one block takes more effort than necessary.

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

Completeness5/5

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

For a mutating intake tool, all the essentials are present: when to use, when not to, duplicate avoidance, parameter formats, and the meaning of 'approved' on write. Return values need not be explained since an output schema exists, and annotations already cover the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description carries the full burden and does: it documents format and semantics for medication_name (brand/generic + strength), start_date (YYYY-MM-DD), dose_amount/dose_unit pairing, times_per_day, product_type with its default and value set, route with examples, and marks prescribed_for and atc_code optional.

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?

States a specific verb and resource — 'Add a medication or supplement the user currently takes' — and pins the resource scope with 'currently takes', which separates it from stop_medication and update_medication. The parenthetical clarifies the write path (stored immediately as approved), so an agent knows exactly what this tool does on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions ('Check get_medications first to avoid duplicates') and an explicit exclusion ('Never use this to change a prescribed dose — that is for the doctor'). It also discloses a downstream dependency (check_medication_safety uses dose fields), which tells the agent why to capture those parameters now.

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