Skip to main content
Glama

Academic Research MCP Server

by dev.workers.steve-corbeil.nexgendata-mcp-proxy

search_google_scholar

Read-only

Query Google Scholar for academic papers, citations, and research articles across all disciplines. Returns paper title, authors, publication venue, citation count, abstract preview, and full-text link if available. Use for comprehensive literature searches, citation tracking, or finding highly-cited works.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms or research topic (e.g. 'machine learning bias', 'climate change economics', 'gene therapy advances')
max_resultsNoMaximum papers to retrieve (default 10, recommended for focused results)

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly and openWorld. Description adds behavioral context (return fields, full-text link availability) 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?

Two efficient sentences: first defines action and scope, second lists returns and use cases. No wasted words.

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?

For a simple two-param tool with no output schema, description provides sufficient context about usage and return fields; missing pagination or sorting details but adequate.

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 descriptions for both parameters; description adds no extra meaning 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 it queries Google Scholar for academic papers, lists specific return fields, and implicitly differentiates from sibling search_arxiv by source.

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?

Provides use cases like comprehensive literature searches and citation tracking, but does not explicitly exclude alternatives like search_arxiv for preprints.

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

All Academic Research MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Both tools search for academic papers, but descriptions clearly differentiate: arXiv focuses on peer-reviewed papers in specific fields, while Google Scholar covers all disciplines with citation metrics. Users can distinguish by domain, but the core purpose is similar.

Naming Consistency5/5

Both tools follow a consistent 'search_' prefix and underscore-separated names indicating the source, creating a predictable pattern.

Tool Count3/5

With only two tools, the server feels minimal but not unreasonable for a focused search service. However, a broader research server might expect additional tools for fetching full text or managing bibliographies.

Completeness3/5

The server covers the core search functionality across two major databases, but lacks tools for retrieving papers by ID, downloading PDFs, or managing references, which are common complementary actions.

Resources