nc-mcp-server

send_message

Send a chat message to a Talk conversation, supporting Markdown, @mentions, replies, and thread creation or continuation.

Instructions

Send a chat message to a Talk conversation.

Supports Markdown formatting. Messages can be up to 32000 characters. Use @mention syntax to mention users: @"user-id" or @"display name".

Threads: pass thread_title to start a new thread with this message as its first message; the thread ID is that message's ID and is returned as thread_id, so pass it as thread_id to keep posting into the thread. An existing message cannot be turned into a thread. thread_title cannot be combined with reply_to or thread_id, and thread_id cannot be combined with reply_to (replying to a message inside a thread posts into that thread anyway).

Args: token: The conversation token. Use list_conversations to find tokens. message: The message text to send (supports Markdown). reply_to: Optional message ID to reply to (default: 0 = not a reply). thread_id: Optional ID of an existing thread to post into without quoting a message (default: 0). Use list_threads to find thread IDs. thread_title: Optional title; when set, the message starts a new thread with this title (default: "" = no new thread). Talk shortens titles longer than 203 characters.

Returns: JSON object of the sent message with its assigned ID, its thread_id (0 when the message is not in a thread) and, for thread messages, thread_title.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes
`message`	Yes
`reply_to`	No
`thread_id`	No
`thread_title`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.0Sep 23, 2026

addedInput schema / properties / thread_id

Added value: +{
+  "default": 0,
+  "title": "Thread Id",
+  "type": "integer"
+}

addedInput schema / properties / thread_title

Added value: +{
+  "default": "",
+  "title": "Thread Title",
+  "type": "string"
+}

First observedv0.7.0Sep 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the minimal annotations (all false), the description reveals important behavior: Markdown support, the 32000-character limit, @mention syntax, the rule that an existing message cannot be turned into a thread, the title-length truncation, and the exact JSON return structure. This gives an agent a realistic model of the tool's side effects and constraints.

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?

The description is well-structured: an opening purpose sentence, a concise feature paragraph, clear constraint lines, a bulleted Args section, and a Returns section. It is longer than average only because it carries substantial necessary context, with no filler or repeated boilerplate.

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?

The tool has complex thread semantics, five parameters, and no useful schema descriptions, yet the description defines all parameter semantics, inter-parameter constraints, default behaviors, and the return format. An agent has everything needed to call it correctly, including prerequisite lookup tools.

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?

With 0% schema description coverage, the description fully compensates: it explains how to obtain token via list_conversations, the meaning of message, the default-0 semantics of reply_to and thread_id, the distinction between starting and continuing a thread, and the >203-character title shortening. Each parameter's purpose and interaction is explicit.

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?

The first sentence 'Send a chat message to a Talk conversation' uses a specific verb and resource and clarifies the domain context, distinguishing it from mail-related and read-only siblings. The additional detail about threading and parameters reinforces a unique operational identity.

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 description gives strong contextual guidance, pointing to list_conversations for tokens and list_threads for thread IDs, and clearly explains when thread_title vs thread_id vs reply_to should be used. It does not explicitly say 'use X instead for reading messages' or otherwise name non-thread alternatives, so it lacks the explicit when-not/alternative contrast that would earn a 5.

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

Deploy Server