Skip to main content
Glama
jhanglim

Mattermost MCP Server

by jhanglim

get_current_user

Retrieve your Mattermost user profile information including username, email, and account details to verify identity and access permissions.

Instructions

현재 토큰 소유자(나)의 정보를 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_current_user' tool. It retrieves the current user information using client.getMe() and returns it as a formatted JSON string in the tool response.
    case "get_current_user": {
      const me = await client.getMe();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              id: me.id,
              username: me.username,
              email: me.email || "",
              first_name: me.first_name || "",
              last_name: me.last_name || "",
              nickname: me.nickname || "",
              full_name: `${me.first_name} ${me.last_name}`.trim() || me.nickname || me.username,
            }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:184-191 (registration)
    Registration of the 'get_current_user' tool in the ListTools response, including its name, Korean description, and empty input schema (no parameters required).
    {
      name: "get_current_user",
      description: "현재 토큰 소유자(나)의 정보를 조회합니다.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for 'get_current_user' tool: an empty object, indicating no input parameters are required.
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Helper method in MattermostClient class that fetches the current user's information from the Mattermost API endpoint '/users/me', used by the tool handler.
    async getMe(): Promise<MattermostUser> {
      return await this.request("/users/me") as MattermostUser;
    }
  • TypeScript interface defining the structure of a MattermostUser object, used for typing the output of getMe() and thus the tool response.
    interface MattermostUser {
      id: string;
      username: string;
      first_name: string;
      last_name: string;
      nickname: string;
      email?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation ('조회합니다'), which implies read-only behavior, but doesn't address authentication requirements, rate limits, error conditions, or what specific user information is returned. The description is minimal and lacks important operational context.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary elaboration. It's appropriately sized for a simple retrieval tool with no parameters, though it could potentially be more front-loaded with key information.

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

Completeness2/5

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

For a user information retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't specify what user information is returned (profile data, permissions, etc.), format of response, or any limitations. The description should provide more context about the return value and operational constraints.

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 with 100% schema description coverage, so the schema already fully documents the parameter situation (none). The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. Baseline for 0 parameters is 4.

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 action ('조회합니다' - retrieve/query) and resource ('현재 토큰 소유자(나)의 정보' - current token owner/my information), making the purpose evident. It doesn't explicitly differentiate from sibling tools like 'get_user_info', but the focus on 'current token owner' provides some implicit distinction.

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

Usage Guidelines3/5

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

The description implies usage context through '현재 토큰 소유자(나)' (current token owner/me), suggesting this tool is for retrieving the authenticated user's own information rather than arbitrary user data. However, it doesn't explicitly state when to use this versus alternatives like 'get_user_info' or provide clear exclusions.

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/jhanglim/mattermost-mcp-server'

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