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),
          },
        ],
      };
    }
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. It mentions the API endpoint and a technical constraint about markdown, but doesn't describe what 'assignables' means (users, groups?), whether this is a read-only operation, what permissions are needed, what the response format looks like, or any rate limits. For a query tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is appropriately concise with two sentences that each serve a purpose: the first states the tool's function and endpoint, the second provides a technical constraint. There's no unnecessary verbosity, though the structure could be slightly improved by front-loading the core purpose more clearly.

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 query tool that interacts with Jira's user assignment system, the description is incomplete. It doesn't explain what 'assignables' are, what the response contains, or important behavioral aspects like authentication requirements or error handling. The technical constraint about markdown is helpful but insufficient for comprehensive understanding.

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% with the single parameter 'project_key' well-documented as 'The id of the project to search'. The description doesn't add any additional parameter semantics beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to given complete schema 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 action ('query assignables') and target resource ('to a ticket on Jira'), with the specific API endpoint provided. It distinguishes from siblings like 'assign_ticket' or 'create_ticket' by focusing on querying rather than modifying. However, it doesn't explicitly differentiate from 'execute_jql' which also queries Jira data.

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 general Jira queries or 'assign_ticket' for actual assignment. It mentions not using markdown in queries, but this is a technical constraint rather than usage context. No explicit when/when-not or alternative tool references are included.

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