Paper Finder

Search papers

search_papers

Read-onlyIdempotent

Use this when the user wants papers on a topic, such as "find recent open-access papers on retrieval-augmented generation evaluation" or "systematic reviews on intermittent fasting". Pass topic words, and optionally from_year, open_access_only and a limit of up to 10. Asks Europe PMC and Crossref together and returns one merged list with each paper's authors, year, venue, DOI, citation count, free full-text link when the index confirms one, and the index it came from. Does not search arXiv: use search_arxiv for preprints. Does not check retractions or reference lists.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of papers to return, 5 by default
`query`	Yes	Topic words, such as "retrieval augmented generation evaluation"
`from_year`	No	Only papers published in this year or later
`open_access_only`	No	Only papers with a free full text; false by default

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	Yes	Date the indexes were read (UTC, YYYY-MM-DD); they are updated continuously
`count`	Yes
`error`	No	Present when status is not ok: a stable code, what went wrong and what to do next.
`notes`	No	Present when one index could not be read
`query`	Yes
`notice`	Yes
`source`	Yes	The indexes the answer was read from
`status`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value by disclosing the federated backend (Europe PMC + Crossref merged), the returned fields, and negative boundaries (no retraction checks, no reference lists). Some of the return-field detail overlaps the output schema, which keeps this at 4 rather than 5.

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?

Front-loaded with the selection trigger and examples, then mechanics, then exclusions. Four sentences, no filler, and each one carries distinct information (trigger, parameters, behavior, boundaries).

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?

For a read-only federated search tool with a full schema and an output schema, the description covers everything an agent needs: when to call it, what to pass, which sources are queried, what comes back, and what it deliberately excludes. No gaps remain.

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 (query, from_year, open_access_only, limit) is already documented with types and bounds in the schema. The description restates the same names and the limit cap of 10 without adding syntax, weighting, or query-construction guidance beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('papers on a topic') with two concrete example queries, and explicitly scopes what it is not ('Does not search arXiv'). The scope and intent are unmistakable and distinguishable from search_arxiv without opening the schema.

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

Usage Guidelines5/5

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

Opens with an explicit 'Use this when the user wants...' trigger complete with realistic example phrasings, and names the alternative tool and the condition that selects it ('Does not search arXiv: use search_arxiv for preprints'). Both when-to-use and when-not-to-use are given.

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

All Paper Finder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.