NestDaddy

research_papers

Read-onlyIdempotent

Scientific papers from arXiv, PubMed, CORE, OpenAlex, CrossRef, Europe PMC and bioRxiv. Returns title, authors, year, abstract and link. limit: 1-50 (default 10).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "research_papers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many results to return, 1-50. Values outside the range are clamped.
`query`	Yes	Topic, method or title words to search for.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedInput schema / properties / limit / description

Added value: +"How many results to return, 1-50. Values outside the range are clamped."

addedInput schema / properties / query / description

Added value: +"Topic, method or title words to search for."

First observedNov 11, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds a useful field list (title, authors, year, abstract, link), but that partly duplicates the existing output schema, and it says nothing about whether all seven sources are queried together, how results are merged/ranked/deduplicated, or any rate-limit behavior across providers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and sources. The trailing limit detail is redundant with the schema, costing a fraction of a point, but there is no filler.

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

Completeness3/5

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

With an output schema and 100% param coverage, the description needn't explain return values, and it doesn't over-reach. However, for a seven-source aggregator it leaves the agent guessing about cross-source merging, ranking, and whether a query hits all providers — context that materially affects result interpretation.

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%, and the description's 'limit: 1-50 (default 10)' simply restates the schema's clamping note. No extra semantics (query matching mode, source narrowing) are added beyond structured fields, so the baseline of 3 applies.

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 names the concrete resource (scientific papers) and enumerates the seven upstream sources (arXiv, PubMed, CORE, OpenAlex, CrossRef, Europe PMC, bioRxiv), which clearly separates it from siblings like news_search and web_search. It lacks an explicit verb such as 'search across' and never states scope/ranking, but an agent can tell what it retrieves.

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

Usage Guidelines3/5

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

Usage is only implied: the source list signals this is the tool for academic literature, and the 'query' param says 'topic, method or title words'. There is no explicit when-to-use vs. when-not, and no routing to web_search or news_search for non-scholarly queries.

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

All NestDaddy 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.