article-review-mcp

by Biogod2020

Overview Schema Source Related Servers Discussions Admin

Submit a revised patch set

article_review_update_patchset

Create a new review round from the same base document, carrying forward decisions and comments on unchanged patches while resetting changed patches to pending for re-review.

Instructions

Create an immutable next review round from the same base document. Exact unchanged patches may carry decisions and reviewer comments; changed patches reset to pending.

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>",
      "patchSet": "<patchSet>"
    },
    "name": "article_review_update_patchset"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`locale`	No
`offset`	No
`status`	No
`topics`	No
`topicId`	No
`baseHash`	No
`patchSet`	Yes
`sessionId`	Yes
`contextMode`	No
`carryDecisions`	No
`idempotencyKey`	Yes
`expectedVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 19, 2026

TDQS

B3.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses key behavioral traits: the round is immutable, unchanged patches carry decisions/comments, and changed patches reset to pending. This is meaningful operational context, though it omits details about idempotency, versioning conflicts, or return behavior.

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?

One dense sentence conveys the core purpose, immutability, and decision/reset behavior without wasted words. It is front-loaded with the action and resource.

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?

Given the high complexity (14 parameters, deep nested patchSet objects, no output schema, no annotations), the description is far too minimal. It covers the central idea but omits lifecycle context, error semantics, concurrency expectations, and parameter meanings, leaving the agent under-equipped.

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?

Schema description coverage is 0%, and the description only explains the patchSet-related semantics (unchanged vs changed patches). Required parameters like sessionId, expectedVersion, idempotencyKey, and the many optional fields are left unexplained. The description does not compensate for the extensive schema.

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 the tool creates a new, immutable review round from the same base document, which is a specific verb+resource pair. However, it does not explicitly distinguish itself from the sibling 'article_review_submit_patchset', leaving some ambiguity about when to use this variant.

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 about when to use this tool versus alternatives like article_review_submit_patchset. The title implies 'revised patch set', but the description does not clarify the intended workflow or exclusions.

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