Nova

Visit checklist

visit_checklist

Read-onlyIdempotent

Generates a caregiver checklist for home visits covering missed doses, symptoms to check, refills, low pill supply, and next appointment.

Instructions

For the home aide (or family visiting): 'What should I do at Rose's today?' Missed doses, recent symptoms to check, refills to pick up, low pill supply and the next appointment.

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

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.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered elsewhere. The description adds the useful behavioral fact that this is an aggregated, pre-visit digest spanning medications, symptoms, refills and appointments, but says nothing about data freshness, scope (single care recipient?) or why certain items appear.

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?

A single tightly packed sentence: the user-intent framing comes first, then the itemized contents. Every clause earns its place and there is no filler.

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 no inputs, the description only needs to convey what questions the tool answers, which it does well by listing the five content areas. The remaining gap is positional context - when this digest is preferable to the sibling briefing/today tools - which keeps it short of a 5.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description wisely spends its words on output contents instead.

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 names a concrete scenario (home aide or family visiting, 'What should I do at Rose's today?') and enumerates the exact items returned: missed doses, symptoms to check, refills, low supply, next appointment. That is far more specific than the name alone, though it never states the verb explicitly ('returns a consolidated visit checklist') and doesn't distinguish it from near-neighbors like get_today or prepare_visit.

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?

Audience framing ('for the home aide or family visiting') implies the usage context, but there is no explicit when-to-use or when-not, and no routing against the many overlapping siblings (get_today, prepare_visit, care_briefing, daily_checkin, recent_activity). An agent must infer the choice from the scenario phrasing alone.

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