Skip to main content
Glama
Sign In
SeaTalk MCP Server

SeaTalk MCP Server

by mukung26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_message_by_message_id

Retrieve a specific message from a group chat using its unique message ID. Obtain the message ID from new mention events.

Instructions

Retrieve a message by its message ID within a group chat thread

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": {
      "message_id": "<message_id>"
    },
    "name": "get_message_by_message_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe ID of the target message, which can be obtained via the event "New Mentioned Message From Group Chat"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states 'Retrieve a message' which indicates a read operation with no side effects, but does not disclose error handling (e.g., if ID is invalid) or performance characteristics. For a simple retrieval, this is minimally adequate.

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 a single, concise sentence that directly states the purpose. No extraneous words, front-loaded with the action and target.

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?

The tool is simple with one parameter and no output schema. The description provides the basic purpose but lacks details on return format or behavior when message is missing. Given the low complexity, it is somewhat complete but could be improved.

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 coverage is 100% with a clear description for message_id. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already provides the needed semantics.

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 description clearly states the verb 'Retrieve' and the resource 'a message by its message ID within a group chat thread', making the tool's purpose unambiguous. It distinguishes from sibling tools like get_chat_history (list messages) and get_thread_by_thread_id (retrieve thread).

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 when a specific message ID is known, especially from the 'New Mentioned Message From Group Chat' event in the parameter description. However, it does not explicitly state when not to use or compare to alternatives like get_chat_history.

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

Deploy Server

Other Tools