jira-lite-mcp

jira_add_comment

Adds a comment to a specified Jira issue using the issue key and plain text body. Preserves line breaks in the comment.

Instructions

Añade un comentario a un issue de Jira. El texto se envía en texto plano y se convierte al formato que espera la API, conservando los saltos de línea.

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

Input Schema

Name	Required	Description	Default
`body`	Yes	Texto del comentario
`issueKey`	Yes	Clave del issue. Ejemplo: ATY-123

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description explains that text is sent in plain text and converted to the API format preserving line breaks, which adds some behavioral context. However, with no annotations provided, the description does not cover potential side effects, auth requirements, or error handling (e.g., what if the issue doesn't exist).

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 consists of two concise sentences. The first states the core purpose, and the second adds a relevant processing detail. No unnecessary words or redundancy.

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?

Given the lack of annotations and output schema, the description is somewhat minimal. For a write tool, it could mention success indicators (e.g., returns comment object) or common constraints. However, for a simple comment-adding operation, it provides the essential information.

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?

The input schema already has 100% coverage with descriptions, but the description adds value by clarifying that the body is processed as plain text with line breaks preserved. This augments the schema's generic 'Texto del comentario' with practical formatting details.

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 clearly states the action (adds a comment) and the resource (Jira issue). The verb 'añade' and resource 'comentario a un issue' are specific, and the tool is easily distinguishable from siblings like jira_create_issue or jira_update_issue.

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 (e.g., when to add a comment vs. a worklog). There are no explicit when-to-use or when-not-to-use instructions, leaving the agent without context for selection.

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

Deploy Server