Skip to main content
Glama

search_papers_bulk

Semantic Scholar: bulk paper search (up to 1000 hits, sortable e.g. 'citationCount:desc' or 'publicationDate:desc', with a continuation token). Filters: fields_of_study, year (e.g. '2020-2024'), venue, publication_types, open_access_pdf.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_papers_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
yearNo
queryYes
tokenNo
venueNo
max_resultsNo
fields_of_studyNo
open_access_pdfNo
publication_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: a 1000-result cap, continuation-token paging, and sort syntax such as 'citationCount:desc'. It omits whether filters combine with AND semantics, whether the token must be sent with the original query, and any rate-limit or auth notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the tool's identity and the highest-value constraints (cap, sort syntax, pagination). The trailing parenthetical filter list is compact and earns its space, though the filter names could be trimmed since they mirror the schema.

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

Completeness3/5

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

For a 9-parameter search tool with no annotations and no output schema, the definition covers volume, sorting, pagination, and filter names. It does not describe what a hit contains or how the token interacts with the other parameters, which an agent needs for multi-page retrieval.

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 0%, so the description must compensate, and it does for the key parameters: it names the filters (fields_of_study, year, venue, publication_types, open_access_pdf), gives a sort format example, and shows a year range format ('2020-2024'). Gaps remain for max_results (only implied by 'up to 1000 hits') and for the token's reuse rules, and the list-style filters have no format 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?

States a specific verb and resource ('bulk paper search') on Semantic Scholar, and the qualifier 'bulk' plus the 1000-hit/pagination detail distinguishes it from the plain search_papers sibling by scale rather than by name. It stops short of explicitly routing the agent away from that sibling.

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 context is implied: this is the high-volume variant, evidenced by 'up to 1000 hits' and 'continuation token'. There is no explicit statement of when to prefer it over search_papers or the recommendation tools, and no prerequisites or exclusions.

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.