Skip to main content
Glama

jira_get_priorities

Retrieve all priority options from your Jira instance to configure issue importance levels and streamline workflow management.

Instructions

Get all available priorities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler case for 'jira_get_priorities' that invokes jiraClient.getPriorities() and formats the response as JSON text.
    case "jira_get_priorities": {
      const priorities = await jiraClient.getPriorities();
      return {
        content: [
          { type: "text", text: JSON.stringify(priorities, null, 2) },
        ],
      };
    }
  • src/index.ts:440-447 (registration)
    Tool registration in listTools handler, including name, description, and empty input schema.
    {
      name: "jira_get_priorities",
      description: "Get all available priorities",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • JiraClient helper method that performs HTTP request to Jira's /priority endpoint to fetch available priorities.
    async getPriorities(): Promise<Array<{ id: string; name: string }>> {
      return this.request<Array<{ id: string; name: string }>>("/priority");
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get' implies a read operation, but it doesn't specify whether this requires authentication, returns paginated results, has rate limits, or what format the priorities come in (e.g., IDs, names, colors). This is inadequate for a tool with zero annotation coverage.

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 no wasted words. It's front-loaded with the core action and resource, making it immediately scannable and perfectly concise for this 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 tool's simplicity (no parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'priorities' means in Jira context, what the return format looks like, or whether this is a global or project-specific operation. For a metadata-fetching tool, this leaves significant gaps.

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 zero parameters, and schema description coverage is 100% (empty schema is fully documented). The description doesn't need to explain parameters, and it correctly implies no inputs are required. A baseline of 4 is appropriate for zero-parameter tools.

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 'Get all available priorities' clearly states the verb ('Get') and resource ('all available priorities'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'jira_get_fields' or 'jira_get_statuses' which follow similar patterns for other Jira entities.

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 (like needing a Jira project context), nor does it explain when you'd need priorities versus other metadata tools like 'jira_get_statuses' or 'jira_get_fields'.

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