Skip to main content
Glama
edrich13

MCP Jira Server

by edrich13

jira_get_current_user

Retrieve details of the currently authenticated user in Jira, including account ID, display name, email, and active status.

Instructions

Get information about the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'jira_get_current_user' tool. Calls JiraClient.getCurrentUser() and returns the user data as JSON.
    case 'jira_get_current_user': {
      const user = await getJiraClient().getCurrentUser();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(user, null, 2),
          },
        ],
      };
    }
  • Registration of 'jira_get_current_user' tool with description and empty input schema.
    {
      name: 'jira_get_current_user',
      description: 'Get information about the currently authenticated user',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • JiraClient.getCurrentUser() method that makes a GET request to /rest/api/2/myself to fetch the current user.
    async getCurrentUser(): Promise<any> {
      const response = await this.client.get('/myself');
      return response.data;
    }
  • src/index.ts:56-297 (registration)
    The tools array contains the full list of tool definitions including 'jira_get_current_user' (line 289-296). The server registers them via ListToolsRequestSchema handler at line 313.
    const tools: Tool[] = [
      {
        name: 'jira_get_issue',
        description: 'Get details of a specific Jira issue by its key (e.g., PROJ-123)',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key (e.g., PROJ-123)',
            },
          },
          required: ['issueKey'],
        },
      },
      {
        name: 'jira_search_issues',
        description: 'Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() AND status != Done"',
        inputSchema: {
          type: 'object',
          properties: {
            jql: {
              type: 'string',
              description: 'JQL query string to search for issues',
            },
            maxResults: {
              type: 'number',
              description: 'Maximum number of results to return (default: 50)',
              default: 50,
            },
          },
          required: ['jql'],
        },
      },
      {
        name: 'jira_create_issue',
        description: 'Create a new Jira issue in a specified project',
        inputSchema: {
          type: 'object',
          properties: {
            projectKey: {
              type: 'string',
              description: 'The project key where the issue will be created',
            },
            summary: {
              type: 'string',
              description: 'Brief summary/title of the issue',
            },
            description: {
              type: 'string',
              description: 'Detailed description of the issue',
            },
            issueType: {
              type: 'string',
              description: 'Type of issue (e.g., Bug, Task, Story, Epic)',
            },
            priority: {
              type: 'string',
              description: 'Priority level (e.g., High, Medium, Low)',
            },
            assignee: {
              type: 'string',
              description: 'Username of the person to assign the issue to',
            },
            labels: {
              type: 'array',
              items: {
                type: 'string',
              },
              description: 'Array of labels to add to the issue',
            },
            components: {
              type: 'array',
              items: {
                type: 'string',
              },
              description: 'Array of component names',
            },
            customFields: {
              type: 'object',
              description: 'Map of additional Jira field IDs/keys (e.g., customfield_10211) to include in the fields payload',
              additionalProperties: true,
            },
          },
          required: ['projectKey', 'summary', 'issueType'],
        },
      },
      {
        name: 'jira_update_issue',
        description: 'Update an existing Jira issue',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key to update',
            },
            summary: {
              type: 'string',
              description: 'New summary/title for the issue',
            },
            description: {
              type: 'string',
              description: 'New description for the issue',
            },
            assignee: {
              type: 'string',
              description: 'Username to assign the issue to',
            },
            priority: {
              type: 'string',
              description: 'New priority level',
            },
            labels: {
              type: 'array',
              items: {
                type: 'string',
              },
              description: 'New array of labels',
            },
            status: {
              type: 'string',
              description: 'New status/workflow state (e.g., "In Progress", "Done")',
            },
            customFields: {
              type: 'object',
              description: 'Map of additional Jira field IDs/keys (e.g., customfield_10211) to include in the fields payload',
              additionalProperties: true,
            },
          },
          required: ['issueKey'],
        },
      },
      {
        name: 'jira_add_comment',
        description: 'Add a comment to a Jira issue',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key',
            },
            comment: {
              type: 'string',
              description: 'The comment text to add',
            },
          },
          required: ['issueKey', 'comment'],
        },
      },
      {
        name: 'jira_get_comments',
        description: 'Get all comments from a Jira issue',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key',
            },
          },
          required: ['issueKey'],
        },
      },
      {
        name: 'jira_get_projects',
        description: 'List all available Jira projects',
        inputSchema: {
          type: 'object',
          properties: {},
        },
      },
      {
        name: 'jira_get_project',
        description: 'Get details of a specific Jira project',
        inputSchema: {
          type: 'object',
          properties: {
            projectKey: {
              type: 'string',
              description: 'The project key',
            },
          },
          required: ['projectKey'],
        },
      },
      {
        name: 'jira_get_issue_types',
        description: 'Get available issue types for a project',
        inputSchema: {
          type: 'object',
          properties: {
            projectKey: {
              type: 'string',
              description: 'The project key',
            },
          },
          required: ['projectKey'],
        },
      },
      {
        name: 'jira_assign_issue',
        description: 'Assign a Jira issue to a user',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key',
            },
            assignee: {
              type: 'string',
              description: 'Username to assign the issue to',
            },
          },
          required: ['issueKey', 'assignee'],
        },
      },
      {
        name: 'jira_delete_issue',
        description: 'Delete a Jira issue permanently',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key to delete',
            },
          },
          required: ['issueKey'],
        },
      },
      {
        name: 'jira_get_current_user',
        description: 'Get information about the currently authenticated user',
        inputSchema: {
          type: 'object',
          properties: {},
        },
      },
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden. It states 'Get information' implying a read operation, but fails to disclose behavioral traits such as authentication requirements, rate limits, or what data is returned.

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 10-word sentence, concise and front-loaded. However, it sacrifices some completeness for brevity.

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?

Given no output schema, the description should explain what information is returned. It only says 'information' without specifics, leaving the agent uncertain about the response format.

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 no parameters (100% coverage). According to calibration, 0 parameters gives a baseline of 4. The description does not add parameter info, but none is 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 verb 'Get' and the resource 'information about the currently authenticated user'. It is distinct from sibling tools which focus on issues, projects, and comments.

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?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied by the name, but the description does not mention any usage context or 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/edrich13/mcp-jira-server'

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