Skip to main content
Glama

Get Jira issue

get_issue
Read-only

Fetch full Jira issue details by key, including comments and attachment metadata, to review or troubleshoot a specific ticket.

Instructions

Get full details for a Jira issue by key (e.g., ONE-123).

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

Input Schema

NameRequiredDescriptionDefault
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.
include_commentsNoInclude the issue's comments.
include_attachmentsNoInclude attachment metadata (IDs, filenames).

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 readOnlyHint=true and openWorldHint=true, so safety and external-dependency profile are covered. The description adds only 'full details', signaling a comprehensive read, but says nothing about the cost of the default include_comments/include_attachments flags turning on or about permissions required to view an issue.

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?

A single front-loaded sentence with the key format example and zero filler. It is efficient, though its brevity leaves the default-on comments and attachments behavior entirely to the schema.

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?

Four well-documented parameters and read-only annotations keep this simple, but with no output schema the description should indicate what 'full details' returns and that comments and attachments are included by default, since that materially changes response size.

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 description coverage is 100%, so every parameter (config_id, issue_key, include_comments, include_attachments) is already documented in the schema. The description only repeats the issue_key example format, adding no new meaning; baseline 3 applies.

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 ('Get full details for a Jira issue') plus the identifier format ('by key, e.g., ONE-123'), so the agent knows it is a single-issue fetch. It does not distinguish itself from retrieval siblings such as search_issues or get_transitions, leaving that differentiation to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: no mention of when to prefer search_issues to find a key first, no prerequisites, no note that the key must already be known. Usage is only implied by the required key argument.

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