nc-mcp-server

set_message_reminder

Idempotent

Set a Talk reminder for a specific message to notify you later; scheduling a new reminder replaces the existing one.

Instructions

Have Talk remind you about a message later with a notification. Replaces an earlier reminder.

Args: token: The conversation token. message_id: The message to be reminded about. remind_at: When, as an ISO 8601 time with time zone, e.g. "2026-10-01T09:00:00+02:00". Must be in the future.

Returns: JSON with token, message_id and remind_at (UTC).

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": {
      "token": "<token>",
      "message_id": "<message_id>",
      "remind_at": "<remind_at>"
    },
    "name": "set_message_reminder"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`remind_at`	Yes
`message_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false (mutating), idempotentHint=true, and destructiveHint=false. The description adds genuinely useful context beyond these: 'Replaces an earlier reminder' explains the idempotent overwrite semantics, and 'Must be in the future' is a hard validation constraint not encoded anywhere else.

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?

Front-loaded purpose sentence, then tight Args and Returns sections with no filler. Every sentence contributes information an agent needs to call the tool correctly.

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?

All three required parameters are documented, the future-time validation and format are stated, and overwrite semantics are disclosed. An output schema exists, so the additional Returns block is a minor bonus rather than a necessity, and nothing needed to invoke the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so well: it defines token as 'The conversation token,' message_id as 'The message to be reminded about,' and remind_at with an explicit ISO 8601 format and timezone example plus a future-time constraint.

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+resource ('Have Talk remind you about a message later with a notification') and distinguishes scope ('a message') from the similarly-named set_file_reminder sibling. Also surfaces the replacement semantics, so an agent can identify it without opening the schema.

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?

Usage is implied by the purpose ('remind you about a message later'), and it notes it 'Replaces an earlier reminder,' which clarifies it is an upsert rather than an additive create. However, it names no alternative or when-not-to-use condition, and does not point to remove_message_reminder or list_message_reminders for the related lifecycle operations.

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

Deploy Server