Skip to main content
Glama
piekstra

Slack MCP Server

by piekstra

get_user_info

Retrieve detailed profile information for a specific Slack user by providing their user ID. This tool enables user management within Slack workspaces.

Instructions

Get detailed information about a specific Slack user.

Args: user_id: The ID of the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main MCP tool handler for 'get_user_info'. It instantiates SlackClient and calls its get_user_info method to fetch user details from Slack API, returning formatted JSON.
    @mcp.tool()
    async def get_user_info(user_id: str) -> str:
        """
        Get detailed information about a specific Slack user.
    
        Args:
            user_id: The ID of the user
        """
        try:
            client = SlackClient()
            result = await client.get_user_info(user_id)
            return json.dumps(result, indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)}, indent=2)
  • Helper method in SlackClient class that performs the actual Slack API call to 'users.info' endpoint to retrieve user information.
    async def get_user_info(self, user_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific user."""
        params = {"user": user_id}
        return await self._make_request("GET", "users.info", params=params)
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'detailed information' but does not specify what details are included, whether authentication is required, rate limits, or error handling. This is a significant gap for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded with the main purpose in the first sentence, followed by a brief parameter explanation. It avoids unnecessary details, though the structure could be slightly improved by integrating the parameter note more seamlessly.

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

Completeness4/5

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

Given the tool's low complexity (single parameter), lack of annotations, and presence of an output schema (which handles return values), the description is reasonably complete. It covers the core purpose and parameter, though it could benefit from more behavioral context to achieve full completeness.

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 description adds meaning by specifying that 'user_id' is 'The ID of the user', which clarifies the parameter's purpose beyond the schema's type definition. However, with 0% schema description coverage and only one parameter, this provides basic but not comprehensive semantic value, aligning with the baseline expectation.

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 resource ('detailed information about a specific Slack user'), making the purpose explicit. However, it does not differentiate from sibling tools like 'list_users' or 'get_team_info', which reduces it from 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 such as 'list_users' for multiple users or 'get_team_info' for team-level data. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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