Nova

Check medications

check_medication

Read-onlyIdempotent

Check today's medication doses and status, learn what a pill treats, and see when and how to take it by name or time of day.

Instructions

Answer 'did I take my evening pills?', 'what is the pink pill for?', 'when do I take metformin?'. Returns today's matching doses with status, plus what each medication is for and how to take it.

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

Input Schema

Name	Required	Description	Default
`medication`	No	Medication name, purpose or description; empty for all
`time_of_day`	No	morning, evening, bedtime or a time; empty for any

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are scoped to today's doses and include dose status plus purpose/administration instructions, which tells the agent what kind of answer to expect.

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?

Three short sentences, front-loaded with the user questions the tool answers, then the output content. Every sentence earns its place; the example phrasing is slightly verbose but directly serves intent matching.

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?

An output schema exists, so return-value structure need not be spelled out, and annotations cover the safety profile. For a two-parameter read-only query tool, the description supplies enough about scope (today), matching (name/purpose/time) and result content for correct invocation.

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 100% and both parameters are already documented as 'medication name, purpose or description; empty for all' and 'morning, evening, bedtime or a time; empty for any'. The sample questions ('pink pill', 'evening pills', 'metformin') illustrate the fuzzy matching but add no syntax or format detail beyond what the schema states, so the baseline 3 holds.

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?

The description gives a concrete verb-resource pair — it returns today's matching doses with status plus each medication's purpose and instructions — and the sample questions make the read-only lookup nature unambiguous. It does not name the obvious siblings (log_medication, check_pill_photo, request_refill), so the contrast is implied rather than stated.

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?

The three example questions imply when to reach for this tool (dose-status checks, 'what is this pill for', 'when do I take X'), which is useful context. However, there is no explicit when-not guidance and no named alternative — an agent must infer that recording a dose belongs to log_medication rather than this tool.

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