armorcode-mcp

Add Comment

armorcode_add_comment

Add a comment to a security finding to document notes or updates. Use dry run to validate the comment without saving.

Instructions

Add comment to finding. dryRun defaults true.

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": {
      "findingId": "<findingId>",
      "note": "<note>"
    },
    "name": "armorcode_add_comment"
  }
}

Input Schema

Name	Required	Description	Default
`note`	Yes
`dryRun`	No
`findingId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The description discloses that 'dryRun defaults true' but does not explain what dryRun does or any other behavioral aspects like whether the comment is appended or if there are side effects; with no annotations, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (7 words) but at the expense of completeness; it conveys the basic action but lacks necessary detail.

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?

For a 3-parameter tool with no output schema, the description is incomplete; it does not explain expected behavior, return values, or prerequisites for adding a comment.

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?

With 0% schema description coverage, the description only mentions 'dryRun defaults true' and does not explain 'note' or 'findingId', adding negligible meaning beyond the schema structure.

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 verb 'Add' and the resource 'comment' to a 'finding', which is specific and distinct from sibling tools like 'armorcode_add_exploitability_comment'.

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 'armorcode_add_exploitability_comment' or other finding actions; the description only mentions a default value.

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

Deploy Server