Skip to main content
Glama
Dsazz

JIRA MCP Server

jira_get_assigned_issues

Retrieve all JIRA issues assigned to you to track tasks and manage workload directly within your IDE.

Instructions

Retrieves all JIRA issues assigned to the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • GetAssignedIssuesHandler class: core implementation executing tool logic by invoking use case, formatting results, and handling specific JIRA errors with enhanced messages.
    export class GetAssignedIssuesHandler extends BaseToolHandler<
      GetAssignedIssuesParams,
      string
    > {
      private formatter: IssuesListFormatter;
    
      /**
       * Create a new GetAssignedIssuesHandler with use case
       *
       * @param getAssignedIssuesUseCase - Use case for retrieving assigned issues
       */
      constructor(
        private readonly getAssignedIssuesUseCase: GetAssignedIssuesUseCase,
      ) {
        super("JIRA", "Get Assigned Issues");
        this.formatter = new IssuesListFormatter();
      }
    
      /**
       * Execute the handler logic
       * Retrieves issues assigned to the current user and formats them
       */
      protected async execute(): Promise<string> {
        try {
          this.logger.info("Getting issues assigned to current user");
    
          // Get assigned issues using use case
          const assignedIssues = await this.getAssignedIssuesUseCase.execute();
    
          // Format the issues using the formatter
          return this.formatter.format(assignedIssues);
        } catch (error) {
          this.logger.error(`Failed to get assigned issues: ${error}`);
          throw this.enhanceError(error);
        }
      }
    
      /**
       * Enhance error messages for better user guidance
       */
      private enhanceError(error: unknown): Error {
        if (error instanceof JiraNotFoundError) {
          return new Error(
            "❌ **No Assigned Issues Found**\n\nNo issues are currently assigned to you.\n\n**Solutions:**\n- Verify you have JIRA issues assigned to your account\n- Check your JIRA permissions\n\n**Example:** `jira_get_assigned_issues`",
          );
        }
    
        if (error instanceof JiraPermissionError) {
          return new Error(
            `❌ **Permission Denied**\n\nYou don't have permission to search for issues.\n\n**Solutions:**\n- Check your JIRA permissions\n- Contact your JIRA administrator\n- Verify you have access to projects\n\n**Required Permissions:** Browse Projects`,
          );
        }
    
        if (error instanceof JiraApiError) {
          return new Error(
            `❌ **JIRA API Error**\n\n${error.message}\n\n**Solutions:**\n- Check your JIRA connection\n- Verify your user account is valid\n- Try again in a few moments\n\n**Note:** This searches for issues assigned to your user account`,
          );
        }
    
        if (error instanceof Error) {
          return new Error(
            `❌ **Search Failed**\n\n${error.message}\n\n**Solutions:**\n- Check your JIRA connection\n- Verify your permissions\n- Try again in a few moments\n\n**Note:** This searches for issues assigned to you`,
          );
        }
    
        return new Error(
          "❌ **Unknown Error**\n\nAn unknown error occurred while searching for assigned issues.\n\nPlease try again.",
        );
      }
    }
  • Tool registration configuration: specifies name, description, empty input schema (params: {}), and binds the handler function.
    {
      name: "jira_get_assigned_issues",
      description: "Retrieves all JIRA issues assigned to the current user",
      params: {},
      handler: tools.jira_get_assigned_issues.handle.bind(tools.jira_get_assigned_issues),
    },
  • Factory function creating the jira_get_assigned_issues ToolHandler wrapper that delegates calls to the instantiated GetAssignedIssuesHandler.
    jira_get_assigned_issues: {
      handle: async (args: unknown) => getAssignedIssuesHandler.handle(args),
    },
  • Tool registry grouping: passes jira_get_assigned_issues to issue tools config factory as part of registration process.
    configs: createIssueToolsConfig({
      jira_get_issue: tools.jira_get_issue,
      jira_get_issue_comments: tools.jira_get_issue_comments,
      jira_get_assigned_issues: tools.jira_get_assigned_issues,
      jira_create_issue: tools.jira_create_issue,
      jira_update_issue: tools.jira_update_issue,
      jira_search_issues: tools.jira_search_issues,
    }),
  • TypeScript interface defining the jira_get_assigned_issues tool handler signature.
    jira_get_assigned_issues: ToolHandler;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves issues but lacks details on permissions required, rate limits, pagination behavior, or response format. This is a significant gap for a tool that likely interacts with an external API and returns data.

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, efficient sentence that directly states the tool's function without any fluff or redundancy. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 the complexity of JIRA API interactions and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, error handling, or what the return data looks like (e.g., issue fields included), leaving gaps for effective tool use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for this scenario is 4, as it avoids unnecessary repetition while being complete for a parameterless tool.

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 ('retrieves') and resource ('all JIRA issues assigned to the current user'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'jira_get_issue' (which gets a specific issue) or 'search_jira_issues' (which allows broader filtering), missing full sibling distinction.

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 when this is appropriate (e.g., for personal task tracking) versus when to use 'search_jira_issues' for more complex queries or 'jira_get_issue' for specific issues, leaving the agent to infer usage 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/Dsazz/mcp-jira'

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