Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Browser SSO login

jira_login
Idempotent

Open browser SSO/SAML/OIDC sign-in for a Jira instance, store session cookies per instance, and retry or check identity if login exceeds waitSeconds.

Instructions

Open a browser window so the user can sign in to a Jira instance that uses auth 'browser' (SSO/SAML/OIDC). Session cookies are stored per instance. If sign-in takes longer than waitSeconds, the window stays open and the login completes in the background — call jira_login again (or jira_whoami) to check.

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

Input Schema

NameRequiredDescriptionDefault
forceNoOpen the browser even if the current session still works.
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.
waitSecondsNoHow long this call waits for the login to finish (default 120).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, but the description goes well beyond them: it explains that session cookies are stored per instance and that after waitSeconds elapses the window stays open and login completes asynchronously. That timeout/background-completion semantics is not inferable from any structured field and is exactly what prevents an agent from misreading an early return as a failure.

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, action first, precondition second, edge-case behavior last. No restatement of the title or the parameter list, and every sentence carries operational information.

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 3 optional, fully documented parameters, no output schema, and annotations carrying the safety profile, the description covers what an agent needs to initiate and re-check a login. It is slightly thin on failure/abort modes (e.g. what a timeout or cancelled sign-in looks like), but nothing critical is missing.

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 description coverage is 100%, so baseline is 3, and the description adds real meaning for waitSeconds by explaining the consequence of exceeding it (window persists, work continues in background). It adds nothing about 'force' or 'instance' beyond the schema, keeping it just above baseline.

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?

States a specific verb and resource ('Open a browser window so the user can sign in to a Jira instance') and narrows it with a precondition — instances using auth 'browser' (SSO/SAML/OIDC). That precondition alone distinguishes it from sibling setup tools like jira_add_instance or jira_logout.

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?

Gives a clear triggering condition (auth mode 'browser') and names follow-up paths (call jira_login again or jira_whoami to poll). It does not explicitly state the inverse case — e.g. what to use for token/basic-auth instances — so the agent must infer the exclusion from the auth-type qualifier.

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