Skip to main content
Glama

jira_get_user

Look up a Jira user by exact username to retrieve their display name, email, timezone, and active status. Use the user search tool when the exact username is unknown.

Instructions

Look up a specific Jira user by their username. Returns display name, email, timezone, and active status. Use jira_search_users if you don't know the exact username.

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": {
      "username": "<username>"
    },
    "name": "jira_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesExact username to look up (e.g., "jsmith", "john.doe")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return payload (display name, email, timezone, active status), which compensates for the absent output schema. It does not discuss permission or visibility constraints (e.g., whether email is hidden by user privacy settings), so it stops short of full behavioral disclosure.

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, front-loaded with purpose, then return values, then routing guidance. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

For a single-parameter read tool with no output schema, the description supplies both the identity semantics and the return shape, plus a fallback path. Nothing an agent needs in order to call it correctly is missing.

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% and the schema already labels the field 'Exact username to look up' with examples, so the description's emphasis on 'exact' adds only marginal reinforcement. Baseline 3 is appropriate when the schema does the parameter work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Look up a specific Jira user by their username') and enumerates the returned fields, so the agent can distinguish it from search-style siblings immediately. No ambiguity about what the tool produces.

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

Usage Guidelines5/5

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

Explicitly names the alternative ('Use jira_search_users if you don't know the exact username'), giving both the condition for this tool (known exact username) and the condition that routes elsewhere. Nothing is left to inference.

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