Skip to main content
Glama
karbassi

slack-mcp

by karbassi

rtm_start

Launch an RTM session to stream live Slack events. Adjust presence awareness, locale, or trim payload with optional parameters.

Instructions

Start a Real Time Messaging session (deprecated, use rtm.connect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
no_latestNoExclude latest timestamps for channels, groups, MPIMs, and IMs to reduce payload size.
mpim_awareNoReturn group-DM (multi-party IM) conversations in the returned data.
no_unreadsNoSkip unread counts for each channel to reduce payload size.
presence_subNoOnly deliver presence events for users subscribed via a ``presence_sub`` event.
simple_latestNoReturn only the latest message timestamp per channel, omitting the full message object.
include_localeNoInclude locale information for users and IMs in the returned data.
batch_presence_awareNoBatch presence deliveries, only for users subscribed via ``presence_sub`` events.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. However, it only mentions deprecation and an alternative, with no details on what 'starting a session' entails, potential side effects, or response behavior. This is insufficient for a tool with 7 parameters.

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 sentence that is front-loaded with the core purpose and deprecation warning. Every part is essential, and there is no wasted text.

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?

While the output schema exists and parameters are fully described, the description lacks context about when it might still be appropriate to use this deprecated tool (e.g., for legacy systems). It is adequate but not comprehensive for agents needing to make informed decisions.

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?

The input schema has 100% description coverage for all 7 parameters, so the baseline is 3. The description adds no additional parameter information, so no uplift beyond the schema.

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 tool starts a Real Time Messaging session, using a specific verb and resource. It also explicitly marks it as deprecated and directs to the alternative rtm_connect, which distinguishes it from siblings.

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

Usage Guidelines5/5

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

The description explicitly states that this tool is deprecated and that users should use rtm.connect instead. This provides clear guidance on when not to use this tool and what alternative to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karbassi/slack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server