Skip to main content
Glama
YGao2005

Scholar Feed MCP Server

Check Watches

check_watches
Read-only

Retrieve new papers matching your watches since the last digest delivery. Optionally scope to a specific watch or check all watches. Read-only and safe to call repeatedly.

Instructions

Pull new matching papers since the last digest delivery, in the same shape as search_papers results. Optionally scope to one watch by watch_name OR watch_id; omit both for all watches. Read-only and idempotent — does NOT advance any watermark (only digest delivery does), so it is safe to call repeatedly (no mark-on-read). This is the in-session 'anything new on my watches?' pull. Requires SF_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watch_nameNoScope to one watch by name. Provide this OR watch_id, or neither for all.
watch_idNoScope to one watch by UUID. Provide this OR watch_name, or neither for all.
limitNoMax hits to return (max 100).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
papersNoMatched / returned papers.
totalNoTotal results available for the query.
pageNo
limitNo
modeNoSearch mode actually applied.
directionNoCitation direction (get_citations: citing | cited_by).
topicNo
noteNo
not_foundNoRequested IDs that had no match.
next_cursorNoKeyset cursor for the next page, or null when exhausted.
hitsNoNew watch matches (check_watches).
resultsNo
Behavior5/5

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

Description adds significant value beyond annotations: it states read-only, idempotent, no watermark advancement, safe to call repeatedly. Annotations only had readOnlyHint=true and destructiveHint=false; description enriches with operational details.

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?

Three concise sentences pack essential information: purpose, scoping, behavioral safety. No fluff; every sentence earns its place.

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 key aspects: return shape, optional scoping, idempotency, auth requirement. Output schema exists so no need to describe return values. Adequate for a read-only list tool with good annotations.

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?

With 100% schema coverage, description adds the mutual exclusivity of watch_name and watch_id and the default behavior of 'all watches'. This clarifies parameter usage beyond schema descriptions.

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 tool pulls new matching papers since last digest delivery, specifying the verb 'pull' and resource 'watches'. It distinguishes from siblings like 'list_watches' by focusing on new results.

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?

It provides clear context for when to use ('in-session anything new on my watches?') and notes that it does not advance watermark, implying repeated safe calls. It explains scoping options but doesn't explicitly contrast with sibling tools.

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