Nova

Get help now

get_help

Alert the entire care circle immediately when an elder needs help due to a fall, feeling unwell, or asking for assistance. Does not contact emergency services.

Instructions

Immediately alert everyone in the care circle that the elder needs help. Use for falls, feeling very unwell, or any request for help. Does not call emergency services.

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_help"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No	What's happening, in the person's words

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already flag a non-idempotent, open-world mutation, and the description adds meaningful context on top: it broadcasts to the whole care circle, is immediate, and deliberately excludes emergency dispatch. It doesn't discuss repeat behaviour or possible alert fatigue, which keeps it short of a 5.

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?

Three tight sentences: what it does, when to use it, and the key limitation – front-loaded and waste-free.

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 annotations, a documented single parameter, and an output schema, the description covers urgency, audience, and the emergency-services boundary. It is essentially complete for an agent deciding whether to trigger it.

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?

Only one parameter and schema coverage is 100%, with the schema explaining the 'reason' field as the person's own words. The description adds nothing about the parameter, which is acceptable at high coverage.

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 audience: 'alert everyone in the care circle that the elder needs help.' That is clearly distinguishable from message-sending or alert-listing siblings, though no sibling is named explicitly.

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?

Gives concrete triggers ('falls, feeling very unwell, or any request for help') and a critical boundary ('Does not call emergency services'). Usage is clear; only a direct pointer to the emergency alternative is missing.

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