Skip to main content
Glama
YGao2005

Scholar Feed MCP Server

Add to Collection

add_to_collection

Add a research paper to a collection using its arXiv ID; collections support nested folders and are created if they don't exist. The paper is automatically saved to your library.

Instructions

Add a paper to a collection, addressed by collection_id OR collection_name (get-or-create by name — no need to look up an id first). Nest with "/": collection_name "AgentOPA/Formal" files the paper under an "AgentOPA" folder. MUTATES: also auto-saves the paper to the library. Idempotent (adding a paper already in the collection is a no-op). Requires SF_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arxiv_idYesarXiv ID of the paper to add, e.g. '2407.15831'.
collection_nameNoName of the collection. Created if it doesn't exist. Use '/' to nest, e.g. 'AgentOPA/Formal'. Provide this OR collection_id.
collection_idNoUUID of an existing collection. Provide this OR collection_name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue when the operation succeeded.
messageNoHuman-readable summary of the outcome.
actionNoMachine label: saved | no_change | removed | liked | created | updated | deleted.
arxiv_idNo
collectionNoThe created/affected collection, when applicable.
watchNoThe created/affected watch, when applicable.
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), description discloses mutation, auto-save to library, idempotency, and API key requirement. No contradiction.

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?

Every sentence is informative: action, addressing method, nesting, mutation note, idempotency, authorization. No wasted words.

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?

Covers purpose, parameters, side effects, idempotency, and authorization. Output schema exists, so return values are not required. Complete for a mutation tool.

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 100%, baseline 3. Description adds meaning: get-or-create by name, nesting with '/', and that collection_id or collection_name are alternatives. Adds value beyond 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?

Clearly states verb (Add), resource (paper to collection), and addressing method (by id or name, with get-or-create by name). Distinguishes from siblings like create_collection and remove_from_collection.

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?

Provides context on when to use (adding paper), mentions get-or-create behavior, auto-save, idempotency, and required API key. Does not explicitly state when not to use, but context is clear.

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/YGao2005/scholar-feed-mcp'

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