Skip to main content
Glama
Sign In
AnonymousOnyx22

Paper Finder MCP

by AnonymousOnyx22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search papers

search_papers
Read-only

Search scholarly papers by keywords and filter or sort results by year, citations, venue, type, and open access to find relevant research and free-to-read links.

Instructions

Search scholarly papers by keywords. Returns title, authors, year, venue, citation count, DOI, a one line abstract and a free to read link when one exists. A showing line under the heading says which results are on this page and how many matched in all, with the page to ask for next, so a long list can be read a page at a time. The results can be ordered, so you can get the most cited papers on a topic or the newest ones, and they can be limited to one kind of paper, to a range of years, to a minimum number of citations or to papers whose title carries the search words, or to one journal or other venue. Inputs: query (required keywords), from_year (optional earliest publication year), to_year (optional latest publication year), min_citations (optional, keep only the papers with at least this many citations), open_access_only (optional, false by default), title_only (optional, false by default, keep only the papers whose title carries the search words), type (optional, journal_article, preprint or book_chapter), venue (optional, a journal or other venue name like Nature, or an OpenAlex source id like S137773608, keep only the papers whose main location is that venue), sort (optional, relevance for the OpenAlex order, cited_by_count:desc for the most cited papers first, or publication_date:desc for the newest papers first), page (optional, which page of results to show, 1 to 400, 1 by default), limit (optional, 1 to 25, default 8). Example prompt: 'find the most cited papers on spaced repetition since 2020.'

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, 1 to 400, 1 by default. Pass the page the showing line names to read the next page.
sortNoHow to order the results. relevance is the OpenAlex order, cited_by_count:desc puts the most cited papers first, publication_date:desc puts the newest papers first.
typeNoKeep only one kind of paper: journal_article, preprint or book_chapter.
limitNoHow many results to return, 1 to 25.
queryYesKeywords, for example: spaced repetition exam performance.
venueNoKeep only papers whose main location is this venue: a journal name like Nature, or an OpenAlex source id like S137773608.
to_yearNoOnly papers published in or before this year.
from_yearNoOnly papers published in or after this year.
title_onlyNoOnly papers with the search words in the title, not just somewhere in the paper.
min_citationsNoOnly papers with at least this many citations.
open_access_onlyNoOnly papers with a free to read copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • addedInput schema / properties / venue
      Added value: +{
+  "description": "Keep only papers whose main location is this venue: a journal name like Nature, or an OpenAlex source id like S137773608.",
+  "minLength": 2,
+  "type": "string"
+}
  2. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, open-world search operation. The description adds useful behavioral detail beyond the annotations: it lists returned fields, explains the showing-line pagination model, and documents ordering and filtering behavior. It does not mention rate limits, authentication, or error behavior, but for a search tool that is a minor gap.

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 front-loaded with purpose, return fields, and pagination behavior, which is good. However, the long 'Inputs:' section largely duplicates the already complete schema, making the overall description longer than necessary. It is informative but not tightly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 11 parameters, 100% schema coverage, and no output schema, the description does a thorough job explaining the return shape, pagination, filters, and defaults. It is nearly complete for an agent to call the tool correctly. It stops short of explaining error cases or explicitly routing among sibling tools, which keeps it from a 5.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already fully documented in the schema. The description repeats the parameters with brief explanations, but adds little semantic meaning beyond what the schema provides. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: searching scholarly papers by keywords. It clearly explains what the tool returns and what filters are available, so the core purpose is unambiguous. However, it does not explicitly distinguish this tool from siblings such as get_papers or find_related_papers, which keeps it from a 5.

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?

The description gives clear usage context: keyword search with optional filters for year, citations, open access, type, venue, sorting, and pagination. The included example prompt ('find the most cited papers on spaced repetition since 2020') reinforces when to use it. It does not explicitly say when not to use it or name sibling alternatives, so it falls short of a 5.

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