Search academic papers from Google Scholar.
Args:
query: Search query string (e.g., 'machine learning').
max_results: Maximum number of papers to return (default: 10).
Returns:
List of paper metadata in dictionary format.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| max_results | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions it returns a list of paper metadata, but does not disclose potential rate limits, authentication requirements, or any limitations. As a read-only search tool, the risk is lower, but the description is still minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured with an Args/Returns format. Every sentence adds value: the main purpose, parameter explanations, and return type. There is no redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter search tool with no output schema, the description covers the essential information: what it does, parameters, and return format. However, it lacks detail on the exact structure of the paper metadata dictionaries and does not mention any usage caveats, which would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, so the description must compensate. It clearly explains both parameters: 'query' with an example and 'max_results' with its default and meaning. This provides complete semantic information beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the verb 'Search' and the resource 'academic papers from Google Scholar', making its purpose explicit. It distinguishes itself from numerous sibling search tools by naming Google Scholar as the source, which is unique among the siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool should be used for searching Google Scholar, but it does not explicitly state when to use it over alternatives or provide any exclusions. There is no mention of alternative tools for other academic sources, leaving the choice somewhat implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools appear to serve the same purpose, such as search_arxiv and search-arxiv, or papers-search-basic, paper-search-advanced, search_papers, and search. The download/read tools for different sources follow similar patterns, but some return 'not supported' messages, making it unclear which tools are actually functional.
Tool names mix snake_case, kebab-case, and bare verbs without a consistent pattern. For example, about_nanci, analysis-citation-network, download-full-paper-arxiv, fetch, and search_arxiv all coexist, and the same action for different sources alternates conventions (search-arxiv vs search_arxiv).
With 53 tools, the server is heavily over-scoped. Many tools are redundant or near-duplicates, such as six source-specific search tools plus an aggregate search, and the inclusion of both paper and clinical trial tools in one server creates unnecessary bloat.
The server covers a wide range of research workflows, including search, download, read, citations, authors, and clinical trials. However, several tools (crossref/pubmed download/read) are non-functional dead ends, and the redundancy makes it harder to navigate the surface.