Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Remove a Jira instance

jira_remove_instance
Destructive

Remove a Jira instance from the current session and optionally delete its stored browser session to manage multi-site configurations.

Instructions

Remove an instance from this session. Optionally also delete its stored browser session.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
deleteSessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that with "from this session" (the instance registration is removed, not the Jira account) and the optional browser-session deletion. It stops short of stating what happens if `name` doesn't exist, whether removing a default instance has side effects, or whether the operation is reversible.

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 with zero padding, and the core action is front-loaded before the optional flag. Nothing is wasted, though the brevity is a contributing factor to the parameter and failure-mode gaps.

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?

For a simple two-parameter destructive tool with no output schema and full annotation coverage, the description covers the essential action and the optional side effect. It is still thin on what the agent needs to call it safely: parameter naming/defaults, behavior on an unknown instance, and effect on the default instance are all absent.

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%, so the description must carry parameter meaning and it only partly does. The second sentence alludes to `deleteSession` without naming it or stating its default, and the required `name` parameter is never explained at all — the agent must guess it is the instance identifier from context.

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?

States a specific verb and resource ("Remove an instance") and scopes it with "from this session," which distinguishes it from jira_add_instance and clarifies the removal is session-local rather than server-side. The purpose is unmistakable, though it doesn't name a sibling directly.

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?

Usage is implied by the phrase "from this session" — a reader infers this undoes jira_add_instance / jira_login for a given instance. There is no explicit when-to-use, when-not-to-use, or pointer to jira_logout as an alternative for session teardown, so the agent must infer routing.

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