Skip to main content
Glama
mukung26

SeaTalk MCP Server

by mukung26

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SEATALK_APP_IDYesYour SeaTalk application ID
SEATALK_APP_SECRETYesYour SeaTalk application secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_employee_profileB

Get an employee's profile by employee ID

get_employee_code_with_emailB

Get an employee's code by email address

check_employee_existenceA

Verify whether employees exist in the organization via SeaTalk ID

get_user_language_preferenceC

Get a user's language preference

get_joined_group_chat_listB

Obtain group chats the bot joined

get_thread_by_thread_idC

Retrieve all messages within a thread of a group chat

get_message_by_message_idA

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

get_chat_historyB

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

get_group_infoC

Get information about a group chat, including member list

send_message_to_group_chatC

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

send_message_to_bot_userC

Send a message to a user via the bot

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a distinct aspect of the SeaTalk domain: employee verification, profile retrieval, various chat operations, and language preference. No two tools have overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., check_employee_existence, get_chat_history, send_message_to_group_chat), making them predictable and easy to navigate.

Tool Count5/5

11 tools cover the core functionalities of an employee and group chat server without being excessive or insufficient. Each tool serves a clear role.

Completeness4/5

The tool surface covers essential operations like employee lookup and chat retrieval/messaging, but lacks update/delete capabilities for messages or group management, which are minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues