Skip to main content
Glama
supuni9622

Research Intelligence MCP

by supuni9622

resolve_paper_access

Determine open access status, landing page, PDF URL, license, and repository for an academic paper. Uses provider and paper ID.

Instructions

Resolve known access information for an academic paper.

The tool retrieves the paper through the selected provider and returns its canonical access metadata, including:

  • open, closed, or unknown access status;

  • landing-page URL;

  • direct PDF URL when available;

  • known license;

  • repository or provider hosting the accessible copy.

This tool resolves metadata only. It does not download, parse, or return the paper PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
providerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesResolved paper title.
accessYesCanonical access status and available URLs.
paper_idYesIdentifier supplied by the caller.
providerYesProvider used to resolve paper access.
identifiersYesPreferred canonical identifier for the resolved paper.
Behavior5/5

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

With no annotations, the description fully discloses behavior: it resolves metadata only, does not download or return PDF. Lists specific return fields, providing complete transparency.

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?

Description is concise, well-structured with bullet points for return data, and front-loads key actions. No redundant sentences.

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?

Given the output schema exists, description adequately covers tool behavior and limitations. It clarifies what the tool does and does not do, making it complete for its complexity.

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

Parameters2/5

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

Schema coverage is 0%, yet description adds no parameter details (e.g., paper_id format, available provider values). This fails to compensate for the schema gap.

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 clearly states it resolves access information for an academic paper, listing specific fields (access status, URLs, license, provider). It distinguishes from siblings like get_paper (metadata) and search_papers (search).

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?

The description indicates the tool resolves metadata only, implying use when access info is needed, not PDF download. However, it lacks explicit when-not-to-use or alternatives beyond siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/supuni9622/research-intelligence-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server