Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Set default Jira instance

jira_set_default_instance
Idempotent

Sets the fallback Jira instance used when a call cannot be routed automatically. Omit the name to clear the default.

Instructions

Choose the instance used when a call cannot be routed automatically. Omit name to clear it.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, open-world mutation, so the safety profile is covered. The description adds real behavioral value by explaining what the setting controls and that omission clears it. It does not say whether the name must correspond to an already-registered instance (e.g., added via jira_add_instance) or what happens on an unknown name.

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 short sentences, front-loaded with the tool's effect and followed by the parameter's edge-case behavior. Nothing is redundant or padded.

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?

For a one-parameter configuration toggle with rich annotations and no output schema, the description covers the essential effect and the omit-to-clear case. The remaining gap is the relationship to instance registration (must the instance already exist?), which would matter for correct invocation.

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?

Schema coverage is 0% and the single 'name' parameter is optional, so the description must supply meaning—and it does, by making explicit the non-obvious semantic that omitting name clears the default rather than leaving it unchanged. It stops short of describing acceptable values or validation.

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 states a specific action on a specific resource ('Choose the instance used when a call cannot be routed automatically'), and explains the routing semantics of the 'default' concept, which distinguishes it from sibling instance-management tools. It does not explicitly name siblings like jira_add_instance or jira_list_instances, so it stops just short of 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 Guidelines4/5

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

It gives a clear condition of relevance: this matters when a call cannot be routed automatically. It also provides actionable guidance for the optional parameter ('Omit name to clear it'), covering both the set and unset paths. It lacks explicit exclusions or a pointer to the alternative of passing an instance per call.

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