article-review-mcp

by Biogod2020

Overview Schema Source Related Servers Discussions Admin

Add categorized reviewer comments

article_review_add_comments

Attach a batch of reviewer comments to existing patches, each tied to a primary topicId, to streamline article patch review.

Instructions

Attach a batch of reviewer comments to existing patches. Each comment must use exactly one primary topicId.

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": {
      "sessionId": "<sessionId>",
      "expectedVersion": "<expectedVersion>",
      "idempotencyKey": "<idempotencyKey>",
      "comments": "<comments>"
    },
    "name": "article_review_add_comments"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No
`status`	No
`topicId`	No
`comments`	Yes
`sessionId`	Yes
`contextMode`	No
`idempotencyKey`	Yes
`expectedVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 19, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description must carry the burden, and it only adds a single note about topicId. It does not disclose idempotency behavior, error handling, or implications of the 'expectedVersion' and 'idempotencyKey' parameters, which are critical for a write operation.

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 brief, which technically makes it concise, but it sacrifices important clarity for brevity. It front-loads the main action but provides too little detail for a tool with 10 parameters.

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 such a complex tool with a nested comments array and no output schema, the description is inadequate. It doesn't clarify batch behavior, partial-failure scenarios, or the meaning of required fields like 'expectedVersion' and 'idempotencyKey', leaving significant gaps.

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

Parameters2/5

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

The schema has 0% description coverage, yet the description only hints at the 'comments' parameter being a batch and the use of 'topicId'. Required parameters like 'sessionId', 'expectedVersion', and 'idempotencyKey' remain unexplained, leaving the agent guessing their semantics.

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 clearly states it attaches reviewer comments to existing patches, indicating the batch nature and the required topicId context. However, it doesn't strongly distinguish itself from the sibling 'add_comment' (singular) tool, though 'batch' helps.

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 given on when to use this tool instead of alternatives like 'article_review_add_comment' or 'article_review_reply_comment'. The description does not mention exclusions, prerequisites, or context where this batch tool is preferred.

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