Skip to main content
Glama
Sign In
SeaTalk MCP Server

SeaTalk MCP Server

by mukung26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_chat_history

Retrieve group chat messages from the last 7 days using the group ID. Supports pagination with a cursor and adjustable page size (1-100).

Instructions

Obtain the group chat history (messages sent within 7 days)

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>"
    },
    "name": "get_chat_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor for pagination
group_idYesThe ID of the group chat
page_sizeNoNumber of messages included in one response (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, description must disclose behavior. It mentions the 7-day window but does not indicate whether the tool is read-only, how pagination works, or if results are sorted. Insufficient for a list tool.

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

Conciseness4/5

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

Single sentence, no extraneous words. Concise but could front-load more critical details without being verbose.

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?

No output schema and no description of return format. For a paginated list tool with cursor and page_size, missing explanation of pagination behavior and default order. Sibling tools mentioned but no differentiation.

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 covers 100% of parameters with descriptions. Description adds no extra meaning beyond schema, so baseline 3 applies. No compensation needed.

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?

Clearly states verb 'Obtain', resource 'group chat history', and a specific constraint 'messages sent within 7 days'. Differentiates from siblings like get_message_by_message_id and get_thread_by_thread_id by focusing on a list of recent messages.

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 information on when to use this tool versus alternatives such as get_message_by_message_id for a single message or get_thread_by_thread_id for a thread. Missing context about prerequisites or comparison to siblings.

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