Nova

Snooze a reminder

snooze_reminder

Re-schedules the caller's current medication reminder by a chosen number of minutes so a dose can be delayed without losing track.

Instructions

'Remind me in 10 minutes.' Re-schedules the latest medication reminder for the caller.

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

Input Schema

Name	Required	Description	Default
`minutes`	No	Minutes from now

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already disclose that the tool is not read-only, not destructive, and not idempotent. The description adds useful context that it targets the latest medication reminder for the caller, but it does not explain whether the existing reminder time is replaced, what happens if no reminder exists, or any permission constraints.

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?

The description is two short sentences with no wasted language. It front-loads a natural-language trigger and then states the core action clearly.

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?

Given the tool's simplicity, one optional parameter, existing annotations, and an output schema, the description is mostly complete. It identifies the action and reminder type but omits edge cases such as no available reminder or reminders that are not medication-related.

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?

The input schema has 100% description coverage and already defines the optional minutes parameter with default, minimum, and maximum values. The description reinforces the 10-minute example but adds no semantic detail beyond what the schema provides, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action (re-schedules) and a specific resource (the latest medication reminder), so the agent can understand what the tool does. It does not explicitly distinguish this from any sibling tool, though no direct snooze alternative appears in the sibling list.

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 quoted phrase "'Remind me in 10 minutes.'" implies a usage trigger for snoozing, but the description gives no explicit when-not conditions or alternatives such as acknowledging or resolving an alert. Usage is therefore only implied.

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