mcp-jira-confluence-corp

by mshegolev

Overview Schema Source Related Servers Discussions Admin

Python

Remote

jira_get_user

Read-onlyIdempotent

Retrieve a Jira user's profile by their username or account ID.

Instructions

Get a Jira user profile by username or accountId.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which cover the safety profile. The description adds the identification mechanism (by username or accountId) but does not disclose any additional behavioral traits such as error handling, rate limits, or field availability. The description does not contradict annotations, but it adds minimal value beyond them.

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 concise sentence that effectively communicates the core function. It is front-loaded with the action and resource, and every word is necessary.

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?

Given the tool's simplicity and the presence of annotations and an output schema, the description is nearly complete. It misses potential details about the return format or common use cases, but it suffices for basic usage. For a read-only lookup tool, it is adequate but not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% because the parameter descriptions are minimal ('Username or accountId'). The tool description does not elaborate on the parameters, e.g., explaining what an accountId is or the expected format. Although there is an output schema, the lack of parameter clarification reduces usability.

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?

The description clearly states the tool's purpose: 'Get a Jira user profile by username or accountId.' It specifies the action (Get), resource (Jira user profile), and identification method, distinguishing it from sibling tools like jira_get_issue or jira_search_issues.

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 usage guidance is provided. The description does not mention when to use this tool over alternatives, nor does it specify any prerequisites or caveats. For a simple retrieval tool, this is insufficient for an AI agent to make optimal decisions.

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