Skip to main content
Glama

Semanticscholar Get Paper

semanticscholar_get_paper
Read-onlyIdempotent

Get full metadata for a single paper by ID. Accepts a Semantic Scholar paper ID, or a prefixed ID like "DOI:10.1145/3292500", "arXiv:2106.15928", or "CorpusId:215416146". Returns abstract, TLDR summary, authors, venue, citation/reference counts, fields of study, and open-access PDF. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paper_id": "DOI:10.1038/s41586-021-03819-2"
    },
    "name": "semanticscholar_get_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYesPaper identifier. A Semantic Scholar ID, or prefixed: "DOI:10...", "arXiv:2106.15928", "CorpusId:...".

Output Schema

NameRequiredDescriptionDefault
doiNoDigital Object Identifier
urlNoURL to the paper
tldrNoTL;DR summary of the paper
yearNoPublication year
titleNoPaper title
venueNoPublication venue
authorsNoPaper authors
journalNoJournal name
abstractNoPaper abstract
paper_idNoSemantic Scholar paper ID
citation_countNoNumber of citations
is_open_accessNoWhether the paper is open access
fields_of_studyNoFields of study tags
open_access_pdfNoURL to open access PDF if available
reference_countNoNumber of references in the paper
publication_dateNoFull publication date
publication_typesNoPublication type tags
influential_citationsNoNumber of influential citations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / authors / items / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "string"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by noting the tool is 'Keyless' (no auth/credential setup) and by enumerating the returned payload, which matters because it is an open-world external lookup.

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?

Three short sentences, front-loaded with purpose, then accepted inputs, then return contents. Every sentence carries distinct information and there is no filler or repetition.

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?

With an output schema present and 100% schema coverage, the definition needs little more than purpose and input formats, and it supplies both. The only missing piece is a hint about what happens on an unresolvable or malformed ID (error versus empty result), which is minor for a read-only lookup.

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% and the single parameter is already documented with the same prefixed-ID guidance. The description repeats those formats with concrete examples but adds no new syntax, validation, or fallback meaning beyond the schema, so 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 opens with a specific verb and resource, 'Get full metadata for a single paper by ID', and the singular scoping distinguishes it from the sibling search tool. It never names an alternative directly, so the differentiation is implied by scope rather than stated.

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 implied by 'by ID' versus a search flow, and the accepted identifier formats make the prerequisite clear, but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to semanticscholar_search_papers for agents who only have a title.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.