Genesis402

Search scholarly papers

genesis402_paper_search

Search scholarly literature in OpenAlex to find research or prior art, returning citation counts, open-access links, and results ranked by relevance or citations.

Instructions

Paid ($0.003 USDC). Search scholarly literature in OpenAlex and get works with citation counts and open-access links. Use to find research, prior art or the most-cited work on a topic. For preprints by recency search arXiv (arxiv-search) and for one known DOI use crossref-doi, both through genesis402_call. Returns up to limit works, ranked by relevance or by citations. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Search terms, e.g. 'zero-knowledge proof rollups' or an exact paper title.
`sort`	No	'relevance' (default) or 'cited' for most-cited first.
`limit`	No	How many works to return, 1 to 50. Defaults to 10.
`from_year`	No	Only works published in or after this year, e.g. 2020. Omit for all years.
`payment_signature`	No	Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.6Oct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only mark it non-read-only and open-world, which says nothing about the two-step payment handshake. The description adds the exact price ($0.003 USDC), the quote-then-sign flow, and the assurance that the first call charges and signs nothing — critical context an agent cannot infer from structured fields.

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?

Price and scope lead, alternatives follow, and the payment mechanics close the block. Four sentences, each carrying distinct information with no filler or repetition of the schema.

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?

With full schema coverage, an output schema handling return values, and the non-obvious payment protocol spelled out, nothing needed to call this correctly is missing. The description is complete for a paid, open-world search tool.

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 q, sort, limit, from_year and payment_signature are already fully documented, including enum values and ranges. The description only restates ranking and result count, adding no syntax or format detail 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 ('Search scholarly literature in OpenAlex') plus what comes back (citation counts, open-access links), and explicitly distinguishes itself from arxiv-search and crossref-doi by use case. An agent can select this over its siblings without opening any 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?

Gives positive routing ('Use to find research, prior art or the most-cited work on a topic') and explicit alternatives with their conditions ('For preprints by recency search arXiv… for one known DOI use crossref-doi'). When-to-use and when-not-to-use are both covered.

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