Skip to main content
Glama
Sign In

Paper Nexus

by us.papernex
OverviewDiscussionsAdmin

Get paper details

get_paper
Read-onlyIdempotent

One paper's details: its authors (Paper Nexus keeps the first five), venue, type, DOI, arXiv id, citation and reference counts, and its most-cited references. Pass a Paper Nexus id or a papernex.us/paper/ link. Pass fields to get only the details of each reference you need.

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": {
      "paper": "<paper>"
    },
    "name": "get_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paperYesA Paper Nexus paper id, or a papernex.us/paper/<id> link
fieldsNoOnly these fields of each reference, to keep the result short; the id always comes back. Leave it out for every field.
referencesNoHow many references to list, most cited first

Output Schema

NameRequiredDescriptionDefault
paperYes
referencesYes
references_indexedNoReferences that are papers in Paper Nexus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: Paper Nexus truncates the author list to the first five, references are returned most-cited-first with a default, and `fields` narrows each reference's payload while the id always comes back.

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?

Two tight sentences with the returned payload front-loaded ahead of the calling instructions. The id/link sentence largely duplicates the schema, which keeps it from a 5, but nothing is padded or redundant.

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?

An output schema exists, so return-value detail is correctly omitted, and the description covers the non-obvious pieces an agent needs: author truncation, the most-cited-first reference ordering, and field narrowing. Minor gaps remain around invalid-id behavior and what happens at references=0.

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 three parameters including the 0-50 range and default of 10. The description only restates the id/link format and the fields behavior, adding little meaning beyond the schema text, so the baseline 3 applies.

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 verb and resource ('One paper's details') and enumerates the payload: authors, venue, type, DOI, arXiv id, citation/reference counts, and most-cited references. That clearly separates it from list-oriented siblings like search_papers or list_citing_papers, though it never names an alternative 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 only implied: the agent must infer that this is the tool for fetching details on an already-known paper, and that lookup/discovery belongs to search_papers. There is no explicit when-to-use or when-not-to-use statement, and no prerequisite or error-handling guidance.

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

All Paper Nexus toolsInspect
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