Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Check Jira connections

jira_whoami
Read-only

Verify Jira connectivity and credentials by calling /myself, checking all configured instances in parallel or a specified instance to confirm access before running operations.

Instructions

Verify connectivity and credentials by calling /myself. Without arguments it checks every configured instance in parallel.

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_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description adds genuine value by disclosing the parallel fan-out across all configured instances when called without arguments, but says nothing about failure modes (partial failures across instances, per-instance error reporting) or what identity data comes back.

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?

Two tight sentences, front-loaded with the core action and followed by the no-argument default. No filler or redundancy.

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

Completeness3/5

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

With one optional parameter and no output schema, the description covers the call and its default scope adequately. It leaves open what is returned per instance and how partial failures surface, which matters for a tool that fans out across multiple configured instances.

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 single instance parameter is fully documented in the schema, including the routing fallbacks. The description's "without arguments" phrasing adds the meaning of omission but restates rather than extends the schema's optionality.

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?

"Verify connectivity and credentials by calling /myself" names a specific action and the underlying endpoint, so an agent knows this is a connectivity/identity check rather than a data fetch. It does not distinguish itself from the related jira_login or jira_list_instances tools, which is the one gap keeping it below a 5.

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?

The second sentence conveys the default usage mode (no arguments = check every configured instance in parallel), which implicitly tells the agent this is a safe pre-flight/diagnostic call. However, it never states when to prefer this over jira_login or jira_list_instances, nor any condition for when-not to use it.

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