Skip to main content
Glama
imnotdev25

paper-mcp

by imnotdev25

Get Paper Metadata

paper_get_metadata
Read-onlyIdempotent

Retrieve comprehensive metadata for an academic paper by title, including authors, abstract, citation count, and more. Queries Semantic Scholar and arXiv.

Instructions

Return comprehensive metadata for an academic paper searched by title.

Queries Semantic Scholar first (richest metadata), then falls back to arXiv.

Returns JSON with: title, authors, abstract, year, venue, doi, arxiv_id, semantic_scholar_id, citation_count, reference_count, fields_of_study, publication_types, publication_date, is_open_access, open_access_pdf, tldr.

Args: params (PaperInput): { paper_title: str }

Returns: str: JSON-encoded metadata dict or { "error": "..." }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYesShared input accepted by every tool in this server.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds value by detailing the two-step query strategy (Semantic Scholar then arXiv) and listing return fields, providing behavioral insight beyond annotations.

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?

Concise and well-structured: opening sentence, source explanation, enumerated return fields, explicit args and returns. No unnecessary text.

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?

Description covers purpose, behavior, return format, and parameters. With annotations and implied output schema, it provides sufficient context for an agent to use the tool correctly.

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% with full parameter description. Description restates the parameter structure but does not add significant new meaning; baseline 3 is appropriate.

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?

Description clearly states it returns comprehensive metadata for an academic paper by title, specifies sources (Semantic Scholar first, arXiv fallback), and distinguishes from sibling tools that focus on citations, fulltext, or PDF.

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?

Description implies use when you have a paper title and need metadata, but does not explicitly state when not to use or compare with alternatives like doi_get_metadata. The fallback behavior provides useful context.

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/imnotdev25/paper-search-mcp'

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