Skip to main content
Glama
CSOAI-ORG

Slack Enterprise MCP Server

set_channel_topic

Update a Slack channel's topic to communicate current focus or announcements. Specify the channel and new topic to quickly align the team.

Instructions

Update the topic of a Slack channel. Provide channel ID or name.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: channel (str): The channel to analyze or process. topic (str): The topic to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
topicYes
api_keyNo
Behavior1/5

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

The behavioral transparency section provides extensive details about read-only, idempotent, and stateless behavior, but these directly contradict the tool's implied mutation purpose (updating a channel topic). Since no annotations are provided, the description is the sole source of behavioral info, and it is incorrect and misleading.

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

Conciseness1/5

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

The description is excessively long and contains much irrelevant information (analysis, classification, rate limits for pro tier) that does not pertain to updating a channel topic. Important details are buried, and the structure is not front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's 3 parameters (2 required) and no output schema, the description fails to explain what the tool returns, error handling specifics, or how to correctly use the parameters. It is completely inadequate for an agent to correctly invoke this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage and the description's 'Args' section merely repeats parameter names (channel, topic, api_key) without adding any semantic meaning. For a tool that updates a Slack channel topic, there is no explanation of what values are valid for channel (ID vs name) or how topic should be formatted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts by stating 'Update the topic of a Slack channel', which matches the tool name, but then immediately contradicts this by describing the tool as 'read-only and stateless' and focused on 'analysis or classification'. This is misleading and fails to clearly state the tool's actual purpose.

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

Usage Guidelines1/5

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

No explicit guidance is provided for when to use this tool for updating a channel topic. The description discusses general analysis use cases, which are irrelevant to the tool's core function, and does not distinguish it from sibling tools like create_channel or send_message.

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/CSOAI-ORG/slack-enterprise-mcp'

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