Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

query_assignable

Find users who can be assigned to Jira tickets in a specific project. Use this tool to identify available assignees when managing task allocation.

Instructions

Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYesThe id of the project to search

Implementation Reference

  • The core implementation of the 'query_assignable' tool handler. It performs an HTTP GET request to Jira's assignable users search endpoint using the provided project_key, returning the list of assignable users or an error.
    async function queryAssignable(project_key: string): Promise<any> {
      try {
        const params = {
          project: project_key, // JQL query string
        };
    
        const response = await axios.get(
          `${JIRA_URL}/rest/api/3/user/assignable/search`,
          {
            headers: getAuthHeaders().headers,
            params,
          },
        );
    
        return response.data;
      } catch (error: any) {
        //return the error in a json
        return {
          error: error.response.data,
        };
      }
    }
  • The schema definition for the 'query_assignable' tool, registered in the ListTools handler. Defines the input schema requiring a 'project_key' string.
      name: 'query_assignable',
      description:
        'Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query.',
      inputSchema: {
        type: 'object',
        properties: {
          project_key: {
            type: 'string',
            description: 'The id of the project to search',
          },
        },
        required: ['project_key'],
      },
    },
  • src/index.ts:904-921 (registration)
    The registration and dispatching logic for the 'query_assignable' tool in the CallToolRequestSchema handler's switch statement. Extracts 'project_key' from arguments and invokes the handler function.
    case 'query_assignable': {
      const project_key: any = request.params.arguments?.project_key;
    
      if (!project_key) {
        throw new Error('Query is required');
      }
    
      const response = await queryAssignable(project_key);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and description only mentions API endpoint. Missing details on permissions, return behavior, or error conditions. The markdown note adds little behavioral context.

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?

One sentence, efficient. The markdown instruction is slightly extraneous but does not harm clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple tool with one parameter. However, lacks explanation of return format or what 'assignable' means, leaving some ambiguity.

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 coverage is 100% with one parameter described. Description does not add meaning beyond the schema, so baseline of 3 is appropriate.

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?

Clearly states querying assignables to a ticket via a specific Jira API endpoint. However, it does not differentiate from sibling tools like 'assign_ticket' or 'execute_jql'.

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?

No guidance on when to use this tool vs alternatives. The only instruction is 'Do not use markdown', which is unrelated to usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.