Paper Nexus

List my library

list_library

Read-onlyIdempotent

The user's own Paper Nexus library: with no collection, its collections and the first papers; with a collection (its name, path such as "Thesis / Methods", or id), the papers directly in it. Pass the paper ids to recommend_papers to explore around them. Page through with cursor; next_cursor is null on the last page. Pass fields to get only the details of each paper you need.

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_library"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No	next_cursor from the previous page
`fields`	No	Only these fields of each paper, to keep the result short; the id always comes back. Leave it out for every field.
`collection`	No	A collection name, path or id

Output Schema

Name	Required	Description
`items`	Yes
`counts`	No
`collection`	No
`collections`	No	Only on a first page without a collection
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral detail: cursor paging with a null next_cursor terminating the result set, and the fact that `fields` trims each paper while the id always returns. Return shape is covered by the output schema.

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?

Four short sentences, front-loaded with the resource and its two modes, then paging, then field selection. Every sentence carries distinct information; nothing restates the name or the annotations.

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

Completeness5/5

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

For a read-only browsing tool with an output schema, annotations and a well-described parameter set, this covers everything an agent needs: which mode returns what, how to address a collection, how to paginate, how to trim results, and where to go next. No meaningful gap remains.

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?

Schema coverage is 75% and already documents limit bounds, cursor, fields and collection. The description still adds value by showing the accepted collection forms (name, path like "Thesis / Methods", or id) and by framing `fields` as a result-size control. Only `limit` gets no narrative treatment, and it is fully described in the schema.

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?

States a specific verb and resource (the user's own Paper Nexus library) and splits the behavior into two clearly defined modes: no collection returns collections plus first papers, with a collection returns the papers directly in it. This distinguishes it from search_papers, which operates on a broader corpus.

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?

Gives concrete when-to-use context for both modes (browse everything vs. drill into a named/path/id collection) and explicitly routes the agent onward: 'Pass the paper ids to recommend_papers to explore around them.' It does not explicitly exclude search_papers for keyword lookups, which keeps it just short of a 5.

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

All Paper Nexus 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.