Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_paper

Fetch a paper by DOI or arXiv ID and ingest it into your research workspace in one step.

Instructions

Fetch a paper by DOI/arXiv ID and ingest it (one-shot).

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": {
      "identifier": "<identifier>"
    },
    "name": "add_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes
clusterNo
no_zoteroNo
skip_verifyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description lacks details on side effects (e.g., duplicate handling, state changes), authentication requirements, or rate limits. 'Ingest' is vague and does not disclose potential behaviors like skipping existing papers or triggering downstream processing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but at the expense of necessary detail for 4 parameters. It is concise but insufficient for comprehensive understanding, missing parameter explanations and usage nuance.

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?

Given the presence of an output schema, return value explanation is not required. However, with 4 parameters and no annotations, the description fails to cover parameter roles or behavioral context, leaving the tool underspecified for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%. The description explains only the 'identifier' parameter as DOI/arXiv ID but ignores 'cluster', 'no_zotero', and 'skip_verify'. Their purposes remain unclear, forcing reliance on parameter names and defaults alone.

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 clearly states the tool fetches a paper by DOI/arXiv ID and ingests it, specifying the action and resource. It distinguishes from sibling tools like 'search_papers' which search by query, but does not explicitly differentiate from other import tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'import_folder_tool' or 'search_papers'. The description only states the basic operation without context of prerequisites or exclusion cases.

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

Deploy Server

Other Tools