Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

List Jira instances

jira_list_instances
Read-only

Lists every configured Jira instance with name, URL, deployment, auth method, mapped projects, and session state, plus the default instance. Call this first to identify which instance to target.

Instructions

List every configured Jira instance (name, URL, deployment, auth method, mapped projects, session state) and the default instance. Call this first when unsure which instance to target.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is supplied by structured data and the description's job is to add context beyond it. It does add the returned field list and the fact that session state and the default instance are exposed, but it says nothing about edge cases such as zero configured instances or what a 'session state' value can be with respect to jira_login. This is useful but not rich 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?

Two sentences with no waste: the first front-loads what the response contains, and the second delivers the invocation rule. The ordering means an agent scanning the first sentence immediately learns it is a read/discovery call.

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, the description carries the burden of explaining the return shape, and its enumerated field list covers that adequately. It is slightly incomplete in that the empty-configuration case and the relationship to jira_login (session state only meaningful after login) are unstated, but the essentials for calling it correctly are present.

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?

There are zero parameters, so no parameter semantics are required; the baseline for an empty schema is 4. The description appropriately spends its words on output content rather than inventing parameter guidance.

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 pairs a specific verb (List) with a specific resource (Jira instances) and enumerates the fields returned (name, URL, deployment, auth method, mapped projects, session state, default instance), which distinguishes it from sibling list tools such as jira_list_projects and jira_list_boards.

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?

It gives an explicit trigger, 'Call this first when unsure which instance to target', which tells the agent when this tool wins. It does not name the counterpart tools for the other paths, e.g. jira_add_instance or jira_set_default_instance when the agent already knows the instance, so the routing is clear for discovery but not fully paired.

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