AgentFeed

Paper by DOI

get_paper

Read-onlyIdempotent

Use when an agent needs the paper behind a DOI. Returns title, year, authors, venue, citation count, open-access URL and the abstract where OpenAlex holds it (CC0 data). The DOI goes in the path as written, slash included: /api/paper/10.1038/nature14539. Costs 0.005 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": {
      "doi": "<doi>"
    },
    "name": "get_paper"
  }
}

Input Schema

Name	Required	Description	Default
`doi`	Yes	a DOI such as 10.1038/nature14539, sent in the path as written (its slash as %2F also works)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026
- addedInput schema / properties / doi / maxLength
```
Added value: +300
```
- addedInput schema / properties / doi / minLength
```
Added value: +7
```
- addedInput schema / properties / doi / pattern
```
Added value: +"10\\.\\d{4,9}(?:\\/|%2[Ff])\\S+"
```

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / doi / description

Previous value: -"a DOI such as 10.1038/nature14539, its slash sent as %2F in the path"New value: +"a DOI such as 10.1038/nature14539, sent in the path as written (its slash as %2F also works)"

AddedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds details annotations cannot express: the data source (OpenAlex, CC0), what is returned and that abstracts are conditional ('where OpenAlex holds it'), and a paid-call cost of 0.005 USDC via x402 with named chains. The payment prerequisite is exactly the kind of behavior an agent must know before invoking.

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 sentences, front-loaded with the usage trigger, then return values, then the path and cost mechanics. No filler and no repetition.

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 covers the return shape and annotations cover safety, so the description fills the remaining gaps an agent needs: payment cost and rails, data provenance/licensing, and the exact path encoding with an example. Nothing material to a correct call is missing.

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% and already documents the DOI pattern, max length, and the %2F alternative. The description restates the path form ('slash included') and adds a concrete example URL, which is mildly useful but largely duplicative, so the 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 ('get the paper behind a DOI') and enumerates the returned fields, which separates it unambiguously from the plural sibling get_papers. An agent can route to it without inspecting either schema.

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 the paper behind a DOI' gives a clear trigger condition, and the enumeration of returned metadata implies the lookup use case. It never explicitly says when to prefer get_papers (search/list) instead, so the exclusion is only implied.

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.