Skip to main content
Glama

jira_get_statuses

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

Instructions

Get all available statuses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that fetches all available Jira statuses by making an API request to the '/status' endpoint.
    async getStatuses(): Promise<Array<{ id: string; name: string }>> {
      return this.request<Array<{ id: string; name: string }>>("/status");
    }
  • MCP server tool call handler for 'jira_get_statuses' that invokes the JiraClient method and formats the response as MCP content.
    case "jira_get_statuses": {
      const statuses = await jiraClient.getStatuses();
      return {
        content: [{ type: "text", text: JSON.stringify(statuses, null, 2) }],
      };
    }
  • src/index.ts:448-455 (registration)
    Tool registration in the listTools handler, defining the tool name, description, and empty input schema (no parameters required).
    {
      name: "jira_get_statuses",
      description: "Get all available statuses",
      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 the full burden of behavioral disclosure. It only states what the tool does ('Get all available statuses') without mentioning whether this is a read-only operation, if it requires authentication, potential rate limits, or what format the statuses are returned in. This leaves significant gaps for a tool in a complex system like Jira.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for a simple tool.

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 and the lack of annotations or output schema, the description is insufficient. It doesn't explain what 'statuses' refer to (e.g., issue statuses), how they're structured, or any behavioral traits like pagination or permissions, leaving the agent with incomplete context for effective 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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to compensate for any parameter gaps, and it correctly implies no filtering or options are required, earning a high baseline score.

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 available statuses'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'jira_get_priorities' or 'jira_get_fields' beyond the resource name, which prevents a perfect score.

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 prerequisites, context for retrieving statuses, or how it relates to other Jira operations like 'jira_get_transitions' or 'jira_get_issue', leaving the agent with minimal usage direction.

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/yogeshhrathod/JiraMCP'

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