Manusights

List manuscript reviews

list_manuscript_reviews

Read-only

Use this when the user asks about their earlier Manusights reviews. Returns the 20 most recent, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_manuscript_reviews"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`reviews`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 30, 2026
- removedOutput schema / properties / reviews / items / properties / created_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reviews / items / properties / created_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / reviews / items / properties / filename / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reviews / items / properties / filename / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / reviews / items / properties / target_journal / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reviews / items / properties / target_journal / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so safety is covered; the description adds real behavioral detail the annotations don't: a fixed cap of 20 results and newest-first ordering. It stops short of 5 because it doesn't say whether older reviews are retrievable at all.

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?

Two sentences, no filler, and the trigger condition is front-loaded before the result-shape detail. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values don't need describing, and the description fills the remaining gap about result count and ordering. The only omission is whether a way exists to see older reviews or narrow the list, which matters for a capped 20-item tool.

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

Parameters4/5

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

The tool takes no parameters, so there is no per-parameter meaning to supply; baseline is 4 by rule. The description correctly avoids inventing parameters that don't exist.

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 states a concrete retrieval action ('Returns the 20 most recent, newest first') and scopes it to the user's own Manusights reviews, which distinguishes it from check_references and journal-policy siblings. It differentiates from get_manuscript_review only implicitly via the list/most-recent framing rather than naming it.

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 this when the user asks about their earlier Manusights reviews' gives a clear triggering condition. It doesn't state when not to use it or point at a sibling for single-review or paginated lookups, so it stops short of the top band.

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

All Manusights tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.