Skip to main content
Glama

add_paper

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

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
clusterNo
no_zoteroNo
skip_verifyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so the description must carry the full burden. It says 'ingest it (one-shot)' but omits side effects, auth needs, or error conditions.

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?

Very concise (one sentence) but under-specified. It sacrifices necessary detail for brevity.

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?

With 4 undocumented parameters and no description of output or prerequisites, the tool description is incomplete for effective use.

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?

Only the 'identifier' parameter is partially explained via 'DOI/arXiv ID'. The other three parameters (cluster, no_zotero, skip_verify) have no explanation, and schema coverage is 0%.

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 clearly states the action (fetch and ingest) and the specific resource (paper) via DOI/arXiv ID. It effectively distinguishes from sibling tools like 'remove_paper' and 'move_paper'.

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 on when to use or not use this tool vs alternatives. For example, it doesn't contrast with 'search_papers' or 'import_folder_tool' for adding papers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WenyuChiou/research-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server