Nova

Message the circle

send_message

Sends a short message to one care-circle member or the whole circle, with an optional urgent flag, so caregivers can coordinate updates and reminders.

Instructions

Send a short message to one person in the care circle or to everyone ('circle').

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": {
      "to": "<to>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	A name, relation ('my daughter', 'Mom') or 'circle' for everyone
`urgent`	No	True only if the sender says it's urgent
`message`	Yes	The message, in the sender'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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is known. The description adds that messages are 'short' and can broadcast to the whole circle, but says nothing about delivery, confirmation, or whether sending to a name that matches multiple people is ambiguous.

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 sentence with zero filler, front-loading the verb and the key scoping distinction (one person vs. everyone). Nothing redundant with the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. However, for an open-world, non-idempotent send operation, the description omits what happens on delivery (who receives it, whether it's immediate, what the sender sees), leaving the agent to infer behavior.

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%; the schema already explains 'to' (name/relation/'circle'), 'message', and the urgent flag. The description reinforces the broadcast value ('circle') but adds no format, length, or edge-case detail beyond the schema, 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 resource ("Send a short message") plus the two targeting modes (one person vs. 'circle'), which separates it from the read-side siblings like read_messages. It does not explicitly name a sibling, but the send-vs-read distinction is inferable from the verb.

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 description implies usage (messaging people in the care circle) but gives no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as read_messages or escalate/alert tools that might be more appropriate for urgent situations.

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