Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__jira_edit_comment

Destructive

Edit an existing comment on 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": {
      "issue_key": "<issue_key>",
      "comment_id": "<comment_id>",
      "comment": "<comment>"
    },
    "name": "atlassian-mcp__jira_edit_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
commentYesNew comment text (plain text, will be converted to ADF)
issue_keyYesThe issue key (e.g. PROJ-123)
comment_idYesThe ID of the comment to edit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations correctly identify a non-read-only, destructive operation, and the description does not contradict them. Beyond those annotations, the description adds no detail about replacement behavior, editing restrictions, or the response; even the plain-text-to-ADF conversion is disclosed only in the schema.

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 single sentence is direct, front-loaded, and free of filler. Its brevity makes it easy to scan, although it leaves several useful operational details unstated.

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?

For a simple, flat four-parameter edit operation, the description, fully documented schema, and annotations are sufficient for basic selection and invocation. It remains sparse because there is no output schema or description of return behavior, and no guidance on obtaining the comment ID or what editing an existing comment entails.

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 all four parameters are already documented, including account selection and comment-text conversion. The description adds no parameter meaning beyond that coverage, making the baseline score appropriate.

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 provides a specific verb and resource and scopes the target to an existing comment on a Jira issue. The operation is clear, but it does not explicitly differentiate this tool from siblings such as jira_add_comment or jira_delete_comment.

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 word 'existing' implicitly indicates that this tool modifies a comment rather than creating one. There is no explicit routing to alternatives, prerequisite guidance, or suggestion to use jira_get_comments to discover the required comment ID.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources