Skip to main content
Glama

Six-agent manuscript review / 论文预审(六智能体)

paper_six_agent_review

Six-agent manuscript review / 论文预审(六智能体) | USE WHEN: the user wants a pre-submission review to find the reasons a paper would be rejected | ALIASES: 预审, 六智能体, 审稿意见, 投稿前审, manuscript review, six agent review | RETURNS: 审稿意见与评分

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": {
      "title": "<title>"
    },
    "name": "paper_six_agent_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes标题
methodsNo方法
resultsNo结果
abstractNo摘要

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety is largely covered. The description adds only 'RETURNS: 审稿意见与评分', with no indication of what the non-read-only behavior does (e.g. whether a review is persisted), how long a six-agent run takes, or whether the paper text is sent externally.

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 pipe-delimited layout front-loads the identity, then USE WHEN, ALIASES, and RETURNS in a scannable order with no filler sentences. The bilingual alias list is somewhat noisy but serves a real disambiguation purpose for Chinese-language requests.

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 4-parameter, single-required-field tool with annotations and no output schema, the description covers purpose and a coarse return hint. It leaves the review output's shape and the meaning of the readOnlyHint=false behavior unexplained, which an agent would want before invoking a multi-agent run.

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% and every parameter carries a short label (标题/方法/结果/摘要), so the schema does the heavy lifting. The description adds no meaning beyond that, such as whether methods/results can be omitted or how much text each field expects. Baseline 3 applies.

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 title and first clause name a specific verb+resource: a six-agent manuscript review producing pre-submission critique. The 'USE WHEN' line reinforces the goal of finding rejection reasons. It does not differentiate from overlapping siblings such as deep_peer_review, pre_submission_review, or proposal_review, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'USE WHEN: the user wants a pre-submission review to find the reasons a paper would be rejected' gives a concrete triggering scenario. However, it offers no exclusions or named alternatives, so an agent facing a similar request cannot tell why it should pick this over pre_submission_review or deep_peer_review.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources