SeaTalk MCP Server

send_message_to_group_chat

Send text, image, or file messages to a group chat using bot integrations. Supports markdown formatting, message quoting, and thread replies.

Instructions

Send a message to a group chat which the bot has been added to

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": {
      "group_id": "<group_id>",
      "message": "<message>"
    },
    "name": "send_message_to_group_chat"
  }
}

Input Schema

Name	Required	Description
`message`	Yes
`group_id`	Yes	The ID of the group chat
`thread_id`	No	The ID of the thread to send the message to
`quoted_message_id`	No	The ID of the message to quote

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.5Jul 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states the basic action without mentioning side effects, permission requirements, rate limits, or what happens if the bot is not in the group. The tool creates a message, but the description does not confirm whether it returns a message ID or confirms delivery.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but arguably too minimal. It front-loads the core action but omits details that could be included without excessive wordiness. A slightly expanded description could improve clarity without sacrificing conciseness.

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

Completeness2/5

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

Given the tool's complexity (nested objects, optional parameters, no output schema), the description is insufficient. It does not address what the tool returns, how to construct the message object, or any constraints (e.g., file size limits). The presence of 10 sibling tools suggests a richer environment, and this description lacks the depth needed for safe selection.

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

Parameters2/5

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

Although the input schema covers most parameters (75% description coverage), the message property itself lacks a description. The tool description adds no new meaning beyond 'send a message', failing to explain the structure of the message object or the meaning of parameters like thread_id and quoted_message_id. It does not compensate for the missing schema description of the message field.

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?

The description clearly states the action ('Send a message') and the target ('group chat which the bot has been added to'). It implicitly distinguishes from the sibling 'send_message_to_bot_user' by specifying the recipient type. However, it does not explicitly contrast itself with that tool or other chat tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, what prerequisites are needed (e.g., bot must be added to the group), or any scenarios where this tool would be inappropriate. The description lacks any usage context or exclusion criteria.

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

Deploy Server