Skip to main content
Glama
health-os

health-os

stop_medication

Idempotent

Record that the user no longer takes a medication: medication_id from get_medications, end_date YYYY-MM-DD (default today; not in the future), stop_reason and side_effects optional (e.g.

Instructions

Record that the user no longer takes a medication: medication_id from get_medications, end_date YYYY-MM-DD (default today; not in the future), stop_reason and side_effects optional (e.g. "course finished", "doctor stopped it", "dose changed"; "rash"). It drops out of get_medications and the safety checks but stays on the timeline as medication_stop. Only when the user says it was stopped — never suggest stopping a medication. If the side effect sounds like an allergic reaction, offer record_allergy too.

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_id": "<medication_id>"
    },
    "name": "stop_medication"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
stop_reasonNo
side_effectsNo
medication_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare idempotent and non-destructive but say nothing about downstream effects; the description supplies them — the medication drops out of get_medications and safety checks yet remains on the timeline as medication_stop. It also states the end_date constraint (not in the future), which is behavioral, not schema, information. No contradiction with annotations.

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?

Front-loaded with the core action, then constraints, then guardrails and escalation — a sensible ordering. The heavy parenthetical example clusters ('course finished', 'doctor stopped it'…; 'rash') make individual sentences dense, but nothing is filler.

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 4-parameter mutation whose output schema already documents return values, the description covers source of IDs, defaults, validation, downstream effects, and a safety escalation path. An agent has everything needed to invoke it correctly and safely.

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%, so the description carries the full burden and does: medication_id is sourced from get_medications, end_date format YYYY-MM-DD with a default of today and a future-date restriction, and stop_reason/side_effects are marked optional with concrete example values. All four parameters gain meaning beyond bare string titles.

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?

Opens with a precise verb+resource: 'Record that the user no longer takes a medication.' This is clearly differentiated from the sibling mutations record_medication and update_medication, which add or edit rather than terminate a medication.

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 an explicit trigger ('Only when the user says it was stopped') and an explicit prohibition ('never suggest stopping a medication'), plus a routing rule to a sibling: 'If the side effect sounds like an allergic reaction, offer record_allergy too.' That is the full when/when-not/alternative triad.

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