Skip to main content
Glama
piekstra

Slack MCP Server

by piekstra

get_team_info

Retrieve workspace details from Slack, including team information and configuration data for integration and management purposes.

Instructions

Get information about the Slack workspace/team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'get_team_info'. It instantiates SlackClient and calls its get_team_info method, serializing the result to JSON or error.
    @mcp.tool()
    async def get_team_info() -> str:
        """Get information about the Slack workspace/team."""
        try:
            client = SlackClient()
            result = await client.get_team_info()
            return json.dumps(result, indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)}, indent=2)
  • SlackClient helper method that performs the actual Slack API call to 'team.info' endpoint.
    async def get_team_info(self) -> Dict[str, Any]:
        """Get information about the Slack workspace/team."""
        return await self._make_request("GET", "team.info")
  • The @mcp.tool() decorator registers the get_team_info function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but lacks details on what information is returned (e.g., workspace name, settings, members), permissions required, rate limits, or any side effects. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no wasted words. It is front-loaded with the core purpose and appropriately sized for a simple tool, making it highly concise and well-structured.

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?

Given that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description's job is reduced. However, as a read operation with no annotations, it should ideally clarify what information is retrieved (e.g., workspace details vs. metadata) to complement the output schema. The current description is minimal but not fully complete for context.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema coverage is 100%, so there is no need for parameter documentation in the description. The description appropriately avoids discussing parameters, which is efficient, but a baseline of 4 is applied since no parameters exist to explain.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'information about the Slack workspace/team', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_channel_info' or 'get_user_info', which target more specific resources, so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone, which is insufficient for optimal selection.

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/piekstra/slack-mcp-server'

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