Skip to main content
Glama

jira_get_assignable_users

Lists users who can be assigned to issues in a specified Jira project, returning only valid assignees with project permissions. Use it before assigning issues to verify eligible users.

Instructions

List users who can be assigned to issues in a specific project. Only users with the appropriate project permissions are returned. Use this before assigning issues to verify valid assignees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectKey": "<projectKey>"
    },
    "name": "jira_get_assignable_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filter to narrow results by name/username
startAtNoStarting index for pagination
maxResultsNoMaximum number of results
projectKeyYesProject key to check assignable users for (e.g., KP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value by stating that only users with appropriate project permissions are returned. However, it says nothing about result limits, pagination defaults, or that the operation is a safe read, leaving gaps for a no-annotation tool.

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?

Three short sentences, each earning its place: purpose, permission constraint, then usage advice. It is front-loaded with the core action and contains no redundant restatement of the tool name.

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

Completeness4/5

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

For a simple, fully-documented four-parameter read tool with no output schema, the definition covers purpose, filtering semantics, and usage timing adequately. The only missing piece is any note on pagination/result-size expectations or read-only behavior, which is minor given the rich schema.

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%, including the projectKey example, query filter, and pagination bounds, so the schema does the heavy lifting. The description only reinforces that the project scope drives the result set and adds no new syntax or format meaning, making the baseline 3 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?

The description gives a specific verb and resource ('List users who can be assigned to issues in a specific project') and adds the permission-scoping qualifier, so the agent knows exactly what comes back. It does not explicitly contrast with the nearby jira_search_users tool, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence gives concrete when-to-use guidance: 'Use this before assigning issues to verify valid assignees.' That is a clear operational context. It stops short of 5 because it names no alternative and no when-not-to-use condition (e.g., when a plain user search is preferable).

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