Rivul

Get full paper metadata

get_paper_details

Read-only

Return the full Rivul Index record for one work by its openalex_id, as given by search_papers: complete snippet, every author held, venue, work type, topic, field, publication date and open-access links. Free under fair-use rate limits. Each call adds 2 to this workspace's MCP usage count, which usage_status reports.

Fields come from the same dated OpenAlex snapshot as search_papers (meta.snapshot_at gives the date) and are not independently verified; publication_date, doi, venue and cited_by_count can be wrong, and some records are corrupted upstream. openalex_id is the stable identifier; a doi may not resolve.

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": {
      "openalex_id": "<openalex_id>"
    },
    "name": "get_paper_details"
  }
}

Input Schema

Name	Required	Description	Default
`openalex_id`	Yes	OpenAlex work id from a search_papers result, e.g. W2626778328 or https://openalex.org/W2626778328.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses fair-use rate limits, a two-unit workspace usage cost reported by usage_status, shared snapshot provenance, and significant data-quality caveats including possible upstream corruption. These are exactly the behavioral details an agent needs before calling a read-only lookup repeatedly.

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?

The description is front-loaded with the core action and return contents, then adds usage cost and data-quality caveats. Every sentence contributes information relevant to correct invocation, and there is no redundant filler.

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 no output schema, the description carries the burden of explaining return values. It lists the returned fields, identifies the snapshot and a metadata field for its date, and warns about unreliable fields and corrupted records, making it complete for a one-parameter lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents the openalex_id format and provenance, so the baseline is 3. The description adds that openalex_id is the stable identifier and that a DOI may not resolve, giving useful semantic guidance for interpreting and preferring the parameter.

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?

The description states a specific verb and resource: return the full Rivul Index record for one work by openalex_id. It enumerates the record contents and distinguishes the tool from search_papers by requiring an ID obtained from search results.

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?

It clearly implies the intended workflow: use an openalex_id returned by search_papers. It does not explicitly state when not to use the tool or contrast it directly with search_papers, but the context is strong and the sibling relationship is clear.

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

All Rivul 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?