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

clawmem-mcp-server

Official
by clawmem-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

issue_comment_add

Add a comment to a GitHub issue to post task output, status updates, or handoff notes for AI agents.

Instructions

Add a comment to an issue so agents can post task output, status, or handoff notes.

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": {
      "issueNumber": "<issueNumber>",
      "body": "<body>"
    },
    "name": "issue_comment_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueNumberYes
bodyYes
replyToCommentIdNo
repoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description only states it 'Add a comment' without disclosing behavioral details like error handling, visibility, or prerequisites. The tool is a write operation but lacks transparency on side effects.

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?

Description is a single, well-structured sentence that conveys the core purpose with no extraneous words. It is front-loaded and efficient.

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?

With 4 parameters, no output schema, and a short description, the tool lacks context on expected behaviors like response format, limitations, or prerequisites. Additional info on comment formatting or error scenarios would be needed for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage, and the description does not explain any parameter meanings. For example, replyToCommentId is not described, leaving agents to infer its purpose from the name alone.

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 'Add a comment to an issue' and its purpose for posting task output, status, or handoff notes. This distinguishes it from sibling tools like issue_comments_list (list comments) or issue_create (create issues).

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 on when to use this tool vs alternatives like issue_comments_list for reading comments, nor when not to use it. The description does not compare with other issue tools or provide 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

Other Tools