Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

get_current_user

Retrieve information about the current authenticated user in Jira, including account details and roles.

Instructions

Get information about the current authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_current_user' tool. Calls jiraClient.getCurrentUser() and returns essential user fields (accountId, displayName, emailAddress, active, timeZone, accountType).
    case 'get_current_user': {
      const user = await jiraClient.getCurrentUser();
    
      // Extract essential fields, improve syntax
      const userData = user;
      const essentialUser = {
        id: userData.accountId, // Shorter field name
        name: userData.displayName, // Shorter field name
        email: userData.emailAddress, // Shorter field name
        active: userData.active,
        timezone: userData.timeZone, // Shorter field name
        type: userData.accountType // Shorter field name
      };
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(essentialUser, null, 2),
          },
        ],
      };
    }
  • Tool definition/schema for 'get_current_user'. Defines name, description, and an empty inputSchema (no parameters needed).
    {
      name: 'get_current_user',
      description: 'Get information about the current authenticated user',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:90-95 (registration)
    Registration/routing in the MCP server: routes 'get_current_user' to handleAssignmentTool.
    } else if (
      name.startsWith('assign_issue') ||
      name.startsWith('get_users') ||
      name.startsWith('get_current_user')
    ) {
      return await handleAssignmentTool(name, args || {}, this.jiraClient);
  • Helper method in JiraClient that calls the underlying Jira API (jira.myself.getCurrentUser()) to fetch current user data.
    // Get current user information
    async getCurrentUser() {
      try {
        const response = await this.jira.myself.getCurrentUser();
        return response;
      } catch (error) {
        throw new Error(`Failed to get current user: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Get information about the current authenticated user', implying a read-only operation with no side effects. However, it does not elaborate on authentication requirements, rate limits, or data sensitivity. The description is minimal but not misleading.

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 sentence, concise and front-loaded. It lacks some specificity (e.g., what 'information' includes), but it is efficient with no wasted words.

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 the tool's simplicity (no parameters, no output schema), the description is minimally complete. It conveys the essential purpose but does not describe the return format or contents, which may be needed for full understanding.

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 input schema has zero parameters, so description is not required to add parameter details. The baseline for 0 params is 4. The description does not provide additional semantics beyond the schema, but none are needed.

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 action 'Get' and the resource 'current authenticated user'. It is specific and distinct from sibling tools like 'get_users', which would list all users. No ambiguity.

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. For instance, it does not clarify that 'get_users' returns all users while this returns only the authenticated user, nor does it suggest prerequisites or context.

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/raalarcon9705/jira-mcp'

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