Skip to main content
Glama
FujishigeTemma

semantic-scholar-mcp

get_authors

Retrieve author details for any academic paper using paper IDs like DOI, arXiv, or Semantic Scholar ID. Customize the returned data with fields such as name, affiliations, and citation count.

Instructions

Get authors information for a specific paper. Use 'fields' parameter to customize author data returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYesThe following types of IDs are supported: - `<sha>` - a Semantic Scholar ID, e.g. `649def34f8be52c8b66281af98ae884c09aef38b` - `CorpusId:<id>` - a Semantic Scholar numerical ID, e.g. `CorpusId:215416146` - `DOI:<doi>` - a Digital Object Identifier, e.g. `DOI:10.18653/v1/N18-3011` - `ARXIV:<id>` - arXiv.rg, e.g. `ARXIV:2106.15928` - `MAG:<id>` - Microsoft Academic Graph, e.g. `MAG:112218234` - `ACL:<id>` - Association for Computational Linguistics, e.g. `ACL:W12-3903` - `PMID:<id>` - PubMed/Medline, e.g. `PMID:19872477` - `PMCID:<id>` - PubMed Central, e.g. `PMCID:2323736` - `URL:<url>` - URL from one of the sites listed below, e.g. `URL:https://arxiv.org/abs/2106.15928v1` URLs are recognized from the following sites: - semanticscholar.org - arxiv.org - aclweb.org - acm.org - biorxiv.org
fieldsNoA comma-separated list of the fields to be returned. The authorId field is always returned. See the resource 'semantic-scholar://fields/author' for available fields. Examples: - `name,affiliations,papers` - `url,papers.year,papers.authors` authorId,name,affiliations,citationCount,hIndex
offsetNoUsed for pagination. When returning a list of results, start with the element at this position in the list.
limitNoThe maximum number of results to return. Maximum is 1000.
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the purpose and that fields can be customized, but omits information on pagination, rate limits, return structure, or any side effects.

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 extremely concise at two sentences, front-loading the purpose and essential customization hint without any superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, no output schema, no annotations), the description is insufficient. It fails to describe that the tool returns a list of authors, the default behavior of pagination, or what the response includes.

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%, providing clear descriptions for all 4 parameters. The description adds minor context about the fields parameter but does not substantially improve understanding beyond the schema.

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 the tool retrieves author information for a specific paper, differentiating it from siblings like get_citation, get_paper, and search_paper. It also mentions the fields parameter for customization.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The agent is left to infer usage from the name and 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/FujishigeTemma/semantic-scholar-mcp'

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