Skip to main content
Glama
Sign In
mcp-server-jira

mcp-server-jira

by kt057
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_issue

Retrieve detailed information for a specific JIRA issue by providing its issue key. Optionally specify which fields to include in the response.

Instructions

JIRA 課題の詳細を取得します

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoFields to include in the response
issueKeyYesIssue key (e.g. PROJECT-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It only states 'gets details,' omitting whether the tool is read-only, what happens with invalid keys, or any side effects. This is insufficient for a fetch operation.

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?

The description is a single, brief sentence in Japanese. It is concise but may benefit from a note about parameter usage or context. There is no waste, but it could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a modest parameter set and no output schema, so the description should compensate. It fails to explain what details are returned or how the `fields` parameter influences output. For a JIRA tool with many siblings, this is incomplete.

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 the schema already documents both parameters. The description adds no meaning beyond the schema, aligning with the baseline of 3.

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 ('JIRA 課題の詳細を取得します') clearly indicates fetching details of a JIRA issue, with a specific verb and resource. However, it does not differentiate from siblings like `search_issues` or `get_transitions`.

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?

No guidance is provided on when to use this tool versus alternatives such as `search_issues`. The description lacks context about prerequisites or appropriate scenarios.

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