Skip to main content
Glama

jira_get_myself

Retrieves profile details of the authenticated Jira user to verify the connection and get the username needed for JQL queries such as assignee = currentUser().

Instructions

Get profile information about the currently authenticated Jira user. Returns display name, email, username, timezone, and active status. Useful for verifying the connection and getting the current user's username for JQL queries like "assignee = currentUser()".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jira_get_myself"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the disclosure burden alone. It establishes this as a read operation by enumerating returned fields, but says nothing about behavior when the session is unauthenticated, whether token scopes affect the response, or error handling. For a zero-parameter read call the risk is low, so this is adequate rather than deficient.

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 tight sentences, front-loaded with the purpose, then the return payload, then the practical use case. No filler or 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?

With no output schema and no annotations, the description compensates by enumerating the returned fields and the primary use case, which is enough for an agent to call it correctly. The only gap is the absence of guidance on the unauthenticated/error path.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter meaning to convey; the baseline for a 0-param tool applies. Nothing in the description misleads about inputs.

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 opens with a specific verb and resource: 'Get profile information about the currently authenticated Jira user.' The qualifier 'currently authenticated' scopes it apart from lookups of arbitrary users, though it never names jira_get_user explicitly as the counterpart.

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

Usage Guidelines3/5

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

It gives positive usage context ('verifying the connection', 'getting the current user's username for JQL'), which is more than nothing. But it offers no when-not guidance and never points to jira_get_user for fetching another person's profile, leaving the sibling split implicit.

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