Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

get_all_statuses

Retrieve all available Jira issue statuses to understand workflow states and track ticket progress across projects.

Instructions

Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_of_resultsNoNumber of results to return

Implementation Reference

  • Handler for the 'get_all_statuses' tool within the MCP server's request handler switch statement. Extracts the number_of_results argument (default 50) and calls getAllStatus to fetch statuses from Jira, returning the JSON response.
    case 'get_all_statuses': {
      const number_of_results = Number(
        request.params.arguments?.number_of_results ?? 50,
      );
    
      const response = await getAllStatus(number_of_results);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema for 'get_all_statuses' with optional number_of_results (integer, default 1). Part of the tools array likely used for registration.
    {
      name: 'get_all_statuses',
      description:
        'Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query.',
      inputSchema: {
        type: 'object',
        properties: {
          number_of_results: {
            type: 'integer',
            description: 'Number of results to return',
            default: 1,
          },
        },
      },
    },
  • Core helper function that performs the API call to Jira's /rest/api/3/status endpoint with maxResults parameter, returns the data or error.
    async function getAllStatus(number_of_results: number): Promise<any> {
      try {
        const params = {
          maxResults: number_of_results, // Adjust as needed
        };
    
        const response = await axios.get(`${JIRA_URL}/rest/api/3/status`, {
          headers: getAuthHeaders().headers,
          params,
        });
    
        return response.data;
      } catch (error: any) {
        //return the error in a json
        return {
          error: error.response.data,
        };
      }
    }
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 but offers minimal behavioral insight. It mentions the API endpoint but doesn't disclose critical traits like authentication needs, rate limits, pagination, or what 'status' entails (e.g., issue statuses, system statuses). The markdown warning is tangential and not a core behavioral trait.

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

Conciseness3/5

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

The description is brief but includes an unnecessary sentence ('Do not use markdown in your query') that doesn't add value for tool understanding. It could be more front-loaded by focusing solely on the tool's purpose and usage context.

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 annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on what 'status' means in Jira context, how results are returned, error handling, or prerequisites. For a tool interacting with an external API, more contextual information is needed.

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?

Schema description coverage is 100%, so the schema fully documents the 'number_of_results' parameter. The description adds no parameter-specific information beyond implying retrieval of 'all' statuses, which might conflict with the parameter's default of 1. Baseline 3 is appropriate as the schema handles parameter documentation.

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 ('all the status on Jira'), specifying the API endpoint '/rest/api/3/status'. It distinguishes from siblings by focusing on status retrieval rather than tickets, attachments, or projects, though it doesn't explicitly contrast with sibling tools.

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 like 'execute_jql' for filtered queries or 'list_projects' for project-related data. It includes an irrelevant instruction ('Do not use markdown in your query') that doesn't help with tool selection.

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/KS-GEN-AI/jira-mcp-server'

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