Genexxis paid agent tools (x402)

research_related_papers

Citation neighbourhood of a seed paper (by DOI, arXiv id, OpenAlex id or query): the seed, OpenAlex related works, most-cited citing works and most-cited references, each with full paper fields. Price: $0.015 USDC per call, paid with x402 on Base.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "research_related_papers"
  }
}

Input Schema

Name	Required	Description
`q`	No	Title or keywords; the best match is used as seed
`doi`	No	DOI, e.g. 10.48550/arXiv.1706.03762
`arxiv`	No	arXiv id, e.g. 1706.03762
`maxItems`	No	1-15 per list, default 10 (higher values are capped)
`openalex`	No	OpenAlex work id, e.g. W2626778328

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses what is returned (seed plus three ranked lists with full paper fields) and a cost/payment trait ($0.015 USDC per call via x402 on Base) that no structured field carries. It omits failure behavior when no seed matches and any rate-limit or latency context.

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?

Two sentences, zero waste, with the functional scope front-loaded and the pricing note appended. Nothing repeats the title or restates the name.

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?

A five-parameter tool with no annotations and no output schema needs to cover return shape and cost, and this does both. The remaining gaps are the implicit requirement of at least one seed identifier (required list is empty) and error behavior when a query has no match.

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 the schema already documents all five parameters including the identifier formats. The description restates the four seed identifier types but adds no syntax, precedence (which identifier wins if several are supplied), or maxItems behavior beyond what the schema says.

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 a specific resource and scope: the citation neighbourhood of a seed paper, broken into related works, citing works and references. That is clearly distinct from the metadata-lookup siblings research_paper and research_papers, though none of them are named explicitly.

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 implied by the seed-paper framing, so an agent can infer this is for citation-graph expansion rather than plain paper lookup. It never states when to prefer this over research_paper or research_papers, and gives no exclusion or prerequisite guidance.

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

All Genexxis paid agent tools (x402) 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.

Resources

Need Help?