Nova

Today's plan

get_today

Read-onlyIdempotent

Retrieve today's medication schedule, upcoming appointments, and unread messages so users or caregivers can see what is due, missed, or next.

Instructions

Today's medication schedule (taken, due, missed, upcoming), the next few appointments and unread messages. Use for 'what's my day look like', 'what pills do I take now', or a caregiver asking about today's plan.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds that results span three resource domains (meds, appointments, messages), but says nothing about freshness, timezone handling, or limits on message counts beyond annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with the content inventory, followed by trigger examples. No filler or redundancy; every clause adds information.

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

Completeness4/5

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

With an output schema present and zero parameters, the description needn't explain return shapes, and the content inventory plus triggers are sufficient to select the tool. Minor gap: it doesn't clarify what 'today' means (timezone/rolling window) for a schedule-oriented tool.

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

Parameters4/5

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

Zero parameters, so no parameter semantics are required and the baseline is 4. The description correctly implies a no-argument, snapshot-style call, consistent with the empty schema.

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?

Names a concrete verb+resource: today's medication schedule with status breakdown, next appointments, and unread messages. It is clearly an aggregated daily summary rather than the single-domain siblings (list_appointments, read_messages, check_medication), though it never explicitly contrasts itself with them.

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

Usage Guidelines4/5

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

Provides concrete trigger phrases ('what's my day look like', 'what pills do I take now') and a caregiver scenario, which is strong usage context. It stops short of exclusions, e.g. not stating that full message history or appointment ranges belong to read_messages/list_appointments.

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