Nova

Doctor visit brief

prepare_visit

Read-onlyIdempotent

Build a one-page brief for a doctor's appointment: changes since the last visit, medication adherence, symptoms by first-seen date, and questions to ask. Helps older adults and caregivers.

Instructions

Prepare a one-page brief for the next doctor's appointment: what changed since the last visit, medication adherence, symptoms with first-seen dates, and specific questions to ask. Works for the elder and caregivers.

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

Input Schema

Name	Required	Description	Default
`appointment`	No	Which appointment (e.g. 'cardiology', 'Dr. Patel'); empty for the next medical one

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds useful behavioral context by specifying the brief's composition (derived, visit-scoped, includes first-seen symptom dates), but says nothing about where the data comes from, freshness/lookback window, or access constraints.

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?

Two tight sentences with the deliverable front-loaded and the contents enumerated without filler. The trailing audience clause is mildly extraneous but earns some place by clarifying caregiver use.

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?

Output schema exists, so return structure needn't be explained, and the description nevertheless previews the sections. With one optional parameter, no required inputs, and read-only annotations, an agent has nearly everything needed; only data-source and lookback 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% and the single optional 'appointment' parameter is fully documented in the schema, including the empty-string default for the next medical appointment. The description adds no parameter guidance beyond that, so baseline 3 applies.

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?

States a specific verb and artifact: 'prepare a one-page brief for the next doctor's appointment', then enumerates its contents (changes since last visit, adherence, symptoms with first-seen dates, questions to ask). An agent can tell this is a synthesis/summary tool rather than a checklist or appointment lister, though it never names the nearest siblings (care_briefing, visit_checklist) to sharpen the boundary.

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?

'Works for the elder and caregivers' signals the audience, and 'next doctor's appointment' implies prep-before-a-visit timing. But there is no explicit when-not-to-use guidance and no routing against care_briefing or visit_checklist, which an agent must disambiguate on its own.

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