Nova

Daily check-in

daily_checkin

Record an elder’s own words about how they feel so Nova can extract mood, pain, sleep, symptoms, and activities, flag concerns, and confirm before alerting family.

Instructions

Record how the person feels in their own words ('I slept badly and I'm a bit dizzy'). Nova extracts mood, pain, sleep, symptoms and activities, checks for red flags, and asks before telling the family about anything concerning. Call this whenever the elder describes how they feel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "how_are_you_feeling": "<how_are_you_feeling>"
    },
    "name": "daily_checkin"
  }
}

Input Schema

Name	Required	Description	Default
`how_are_you_feeling`	Yes	What the person said about how they feel, verbatim

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the downstream pipeline: Nova extracts mood, pain, sleep, symptoms and activities, runs red-flag checks, and asks for consent before telling the family. That consent-gating behavior is important and not derivable from the readOnlyHint=false / destructiveHint=false flags. It does not mention persistence or what the returned confirmation looks like, though an output schema covers that.

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 sentences, each doing work: an example of the input, the processing/consent behavior, and the invocation trigger. Front-loaded with the core action. The middle sentence is dense but every clause (red flags, family notification consent) carries real decision value.

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?

For a single-required-param tool with annotations and an output schema, the description supplies everything an agent needs: the input form, the trigger condition, the extraction behavior, and the consent gate around family sharing. Nothing material is left to inference.

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?

Schema coverage is 100% and the property already says 'verbatim', so the baseline would be 3. The description adds value by reinforcing the expected register with a natural-language example ('I slept badly and I'm a bit dizzy'), making clear this is raw first-person speech rather than a structured summary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource ('Record how the person feels in their own words') and illustrates it with a concrete verbatim example. It also distinguishes itself implicitly from structured siblings like log_vitals by emphasizing free-form self-report, so an agent can tell what kind of input belongs here.

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?

The final sentence gives an explicit trigger: 'Call this whenever the elder describes how they feel.' That is clear context for invocation. It does not name when NOT to use it or point to a sibling (e.g., log_vitals for measured values), so it stops short of full alternative routing.

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