babybuddy-mcp

Official

Overview Schema Source Related Servers Discussions Admin

medications_create_medication

Record a child's medication administration with dosage, unit, time, and notes. Use child ID to attach the entry and schedule the next dose interval.

Instructions

Record a medication administration for a child.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Medication name
`tags`	No	List of tag names to apply
`time`	No	Time administered in ISO 8601 format (e.g. 2024-01-15T14:30:00). Defaults to now.
`notes`	No	Optional notes
`dosage`	No	Dosage amount
`child_id`	Yes	ID of the child. Use list_children to get IDs.
`dosage_unit`	No	Dosage unit: mg, ml, tablets, drops
`next_dose_interval`	No	Interval until the next dose as a duration string (e.g. '04:00:00' for 4 hours)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It merely says 'Record' without disclosing whether it appends a new record, requires the child to exist, or has any side effects. This is minimal behavioral disclosure.

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?

The description is a single, front-loaded sentence with no wasted words. It earns its place by stating the core action, though it is very terse for a tool with 8 parameters.

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

Completeness2/5

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

With no annotations, 8 parameters, and no usage or behavioral context, the one-sentence description is not complete enough for an agent to confidently invoke the tool. The output schema helps, but important contextual details are missing.

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 description coverage is 100%, so the schema already documents all 8 parameters. The description adds no parameter meaning beyond 'for a child', so the baseline score of 3 is appropriate.

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 uses a specific verb ('Record') and resource ('medication administration') scoped to a child. This clearly distinguishes the tool from siblings like medications_update_medication, medications_delete_medication, and medications_list_medications.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, no preconditions, and no exclusions. An agent must infer from the tool name and sibling list when this is the right choice.

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

Deploy Server