OpenPapers

Add paper to collection

add_paper_to_collection

Add an existing verified paper to a persistent local collection, enabling organized research workflows.

Instructions

Add an existing verified paper to a persistent local collection.

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": {
      "collection_id": "<collection_id>",
      "paper_id": "<paper_id>"
    },
    "name": "add_paper_to_collection"
  }
}

Input Schema

Name	Required	Description	Default
`paper_id`	Yes
`collection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden and does add some signal: the collection is persistent and local, and the paper must already exist and be verified. However, it leaves undiscussed mutation-related behavior such as duplicate handling, idempotency, failure when the collection does not exist, and access requirements.

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?

The description is a single front-loaded sentence with no filler or repetition of the title beyond the necessary verb and object. Every phrase earns its place by adding a relevant qualifier: existing, verified, persistent, local.

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?

For a low-complexity tool with two required string IDs, no output schema, and no enums/nesting, the description provides sufficient context to select and invoke the operation. The main omission is guidance about edge cases, but that is less critical given the simple add-to-collection scope.

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?

Input schema shows only paper_id and collection_id strings with no descriptions (0% coverage), so the description must compensate. It does indirectly: paper_id refers to an existing verified paper and collection_id refers to a persistent local collection. It does not relate the parameters with explicit field names, but the tool name and sentence make the mapping recoverable.

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 specific action ('Add'), an object ('existing verified paper'), and a destination ('persistent local collection'), so the core operation is unmistakable. It is implicitly distinct from sibling operations like removing, creating, or verifying, though it does not explicitly contrast itself with any sibling.

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

Usage Guidelines3/5

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

The description only implies when to use it: when a user has an already verified paper and wants to place it into a persistent local collection. It does not name alternatives such as create_collection for missing collections or remove_paper_from_collection for removals, nor does it state explicit when-not-to-use conditions.

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