Skip to main content
Glama

Semanticscholar Search Papers

semanticscholar_search_papers
Read-onlyIdempotent

Search 200M+ academic papers on Semantic Scholar by keyword or exact title. Returns titles, authors, year, venue, CITATION COUNTS, DOI, and open-access PDF links. PREFER for "how many citations does have", "citation count for ", "how cited is ", search the title and read citationCount off the match. Optionally filter by year range and field of study. 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": {
      "year": "2023",
      "limit": 10,
      "query": "transformer attention mechanism"
    },
    "name": "semanticscholar_search_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFilter by publication year or range, e.g. "2023" or "2020-2024".
limitNoMax results to return (default 10, max 25).
queryYesSearch query, e.g. "transformer attention mechanism" or "CRISPR gene editing".
fields_of_studyNoFilter by field of study, e.g. "Computer Science", "Medicine", "Biology", "Physics".

Output Schema

NameRequiredDescriptionDefault
queryNoThe search query used
totalYesTotal number of matching papers
papersYesList of papers matching the search
returnedNoNumber of papers returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / papers / items / properties / authors / items / properties
      Removed value: -{
      -  "id": {
      -    "description": "Author ID",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "description": "Author name",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • changedOutput schema / properties / papers / items / properties / authors / items / type
      Previous value: -"object"New value: +"string"
    • changedOutput schema / required
      Previous value: -[
      -  "query",
      -  "total",
      -  "returned",
      -  "papers"
      -]New value: +[
      +  "total",
      +  "papers"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context beyond annotations, such as 'Keyless' (no API key required) and the fields returned including citation counts and open-access PDF links. It does not mention rate limits or how to disambiguate multiple matches when reading citation counts.

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 compact and front-loaded: it starts with the core action, then returns, then preferred use case, then filters and keyless note. Every sentence contributes useful information without redundancy.

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?

Given the output schema and annotations cover return values and safety, the description is largely complete for a search tool. However, it omits minor behavioral details such as result ordering, pagination, or how to choose among multiple title matches when reading citation counts.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that the query supports 'keyword or exact title' and that year range and field-of-study are optional filters, going slightly beyond the schema's examples.

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 states a specific verb and resource: 'Search 200M+ academic papers on Semantic Scholar by keyword or exact title.' This clearly identifies what the tool does. It does not explicitly name sibling tools or explain how it differs from alternatives like semanticscholar_get_paper, so it falls short of full sibling differentiation.

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?

It gives clear context for use: 'PREFER for "how many citations does <paper title> have"...' and mentions optional year and field-of-study filters. However, it does not specify when not to use this tool or name alternative tools for related tasks.

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.