paperlib-mcp

by polarizetech

Overview Schema Source Related Servers Discussions Admin

Python

Local

search

Search all configured literature providers to find papers and see which ones you already hold.

Instructions

Search all configured literature providers and mark papers already held.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`include_closed`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

B3.3/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 burden. It does disclose a notable behavior beyond the name: it searches all configured providers and marks papers already held. However, it does not say whether marking is persistent, whether external providers are queried live, or whether side effects are possible.

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 sentence that front-loads the action and scope, then adds the distinguishing 'mark papers already held' behavior. Every word earns its place with no redundancy.

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?

The tool has three parameters, no annotations, and zero parameter documentation, yet the description only covers the general action. It leaves include_closed unexplained, does not define what 'already held' means, and omits any operational caveats. The output schema covers return shape, but invocation semantics are incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no meaning for query, limit, or include_closed. The agent must infer the semantics of include_closed and limit entirely from names/defaults, with no compensating detail in the description.

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?

The description uses a specific verb ('Search') and a specific resource ('all configured literature providers'), and adds a distinct behavioral outcome ('mark papers already held'). This clearly separates it from siblings like fetch, library, and providers without needing to inspect schemas.

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?

'Search all configured literature providers' implies this is the cross-provider discovery tool, but the description never explicitly says when to use search versus siblings like fetch or library. Usage context is only implied, with no exclusions or alternative routing.

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

Deploy Server