AgentFeed

Paper search

get_papers

Read-onlyIdempotent

Use when an agent needs scholarly papers on a topic. Returns OpenAlex works (CC0 data) for a search: title, year, DOI, authors, venue, citation count and open-access link, up to 25, optionally from a given year. Cached 24 hours. Costs 0.015 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

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": {
      "q": "<q>"
    },
    "name": "get_papers"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	the search text, up to 200 characters
`limit`	No	papers returned, 1-25, default 10
`year_from`	No	earliest publication year, e.g. 2022

Output Schema

Name	Required	Description	Default
`data`	Yes	the get_papers payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_papers
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +25
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / year_from / maximum
```
Added value: +9999
```
- addedInput schema / properties / year_from / minimum
```
Added value: +1000
```
- changedInput schema / properties / year_from / type
```
Previous value: -"number"New value: +"integer"
```
AddedOct 14, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the 24-hour cache, the hard cap of up to 25 results, and — critically — that calls cost 0.015 USDC via x402 on named chains. Payment/auth requirements are exactly the kind of behavioral context annotations cannot convey.

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?

Front-loaded with the 'Use when' trigger, then return contents, then caching and cost. Dense but every clause carries information; the payment parenthetical is long but necessary and correctly placed last.

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?

Output schema exists, yet the description still summarizes returned fields, and it covers caching, result cap, optional year filter and per-call cost. An agent has everything needed to decide and invoke correctly.

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 coverage is 100%, so q, limit and year_from are already fully documented. The description only restates 'up to 25, optionally from a given year' without adding format or syntax beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ('returns OpenAlex works for a search') and enumerates the returned fields, so the agent knows it is a topical scholarly search. It does not explicitly differentiate itself from the sibling get_paper (singular), leaving the search-vs-detail split implicit.

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?

'Use when an agent needs scholarly papers on a topic' gives a clear triggering condition and the optional year filter is noted. There are no explicit exclusions or named alternatives (e.g., points to get_paper for full text), so it stops short of full routing guidance.

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

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