Skip to main content
Glama
Sign In
SeaTalk MCP Server

SeaTalk MCP Server

by mukung26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_joined_group_chat_list

Retrieve a paginated list of group chats the bot has joined, using cursor-based pagination and adjustable page size.

Instructions

Obtain group chats the bot joined

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_joined_group_chat_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor for pagination
page_sizeNoNumber of items included in one response (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It doesn't mention that the tool is read-only, that results are paginated (despite having 'cursor' and 'page_size' parameters), or any authentication requirements.

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 and concise, but it lacks necessary information to be truly helpful. It could be more informative without being longer.

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?

The description is too minimal for a tool with pagination. It doesn't explain return format, pagination behavior, or error conditions. Sibling tools are not differentiated.

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% (both parameters described in schema). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Obtain group chats the bot joined' clearly states the verb 'obtain' and the resource 'group chats the bot joined'. It distinguishes from siblings like 'get_group_info' (specific group) and 'get_chat_history' (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 guidance on when to use this tool versus alternatives. For example, it doesn't explain when to use this over 'get_group_info' or other getter tools.

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