Skip to main content
Glama
Sign In
MCP Jira Server

MCP Jira Server

by vuphuongminh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jira_add_comment

Adds a comment to a Jira issue using its issue key and comment text, enabling updates or notes on existing tickets.

Instructions

Add a comment to a Jira issue

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>",
      "comment": "<comment>"
    },
    "name": "jira_add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesThe comment text to add
issueKeyYesThe Jira issue key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Add' implies mutation, but it does not disclose whether permissions are needed, whether comments are appended to existing ones, or what happens on invalid issue keys. It is not contradictory, but it is minimal.

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, tightly worded sentence with the action front-loaded. Every word contributes to meaning, with no redundant or filler content.

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?

The tool is simple with two self-explanatory parameters and full schema coverage, so the description plus schema are mostly adequate. However, the absence of any output schema or behavioral context leaves some uncertainty about return values and side effects, preventing a higher score.

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%, with issueKey and comment both described in the schema. The tool description adds no extra meaning beyond what the schema already states, so the baseline score 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?

The description uses a specific verb 'Add' and a clear resource 'a comment to a Jira issue,' making the tool's function unambiguous. It is easily distinguished from siblings like jira_create_issue (creates an issue) and jira_get_comments (retrieves comments).

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It does not mention that the issue must exist, that comments are appended, or that jira_get_comments would be the read counterpart.

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