Skip to main content
Glama
Sign In
Jira MCP Server

Jira MCP Server

by Eliya-56
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_task_details

Retrieve full context for a Jira issue, including description, status, assignee, and comments, to understand its current state and history.

Instructions

Get full context for a Jira issue including description, status, assignee, and comments.

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

Input Schema

NameRequiredDescriptionDefault
issue_keyYesJira issue key (e.g. PROJ-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly signals a read operation and specifies the returned content, but it does not mention behavior for invalid issue keys, permissions, or whether comments are fully expanded or truncated.

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?

The description is a single, concise sentence that front-loads the operation and expected result. Every word contributes value, and there is no filler or redundant restatement of the tool name.

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 simple one-parameter retrieval tool with no output schema, listing the returned categories gives the agent enough context to set expectations. It could note the lack of an explicit response shape, but the low complexity and full schema coverage make that a minor gap.

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?

The single issue_key parameter is fully documented in the schema with a pattern and example, giving 100% schema coverage. The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 the specific action 'Get full context for a Jira issue' and enumerates the key fields returned: description, status, assignee, and comments. This clearly distinguishes it from sibling list/search tools like get_my_tasks and search_tasks, which operate at a different granularity.

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?

The description implies use when the agent needs complete details on a single known issue, but it never explicitly names alternatives or states when not to use it. The distinction from get_my_tasks and search_tasks is inferable from sibling names, not stated.

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

Deploy Server

Other Tools