google-surf-mcp

by HarimxChoi

Overview Schema Related Servers Score Discussions

TypeScript

Local

Google Scholar Search

scholar_search

Retrieve academic paper metadata—authors, venue, year, citation count, and full-text links—from Google Scholar queries.

Instructions

Use only for paper metadata such as authors, venue, year, versions, and citation counts. With research enabled, one local broker lets multiple MCP sessions query the same knowledge base concurrently and orders writes safely. Do not use it to discover or read paper content; use search with extract_mode instead. Returns title, authors, publication, year, snippet, citation count, related/version links, and an available full-text link. With research enabled, metadata and citation observations retain provider provenance and research_context exposes related prior searches. Google Scholar uses browser search, SearchApi primary, or configured fallback. Results are cached with the same TTL as search. Max 10 papers per call.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum papers. Integer 1-10, default 10.
`query`	Yes	Google Scholar query. Supports quotes and author: operators.
`project_id`	No	Project memory id.
`session_id`	No	Stable host task id. Reuses the same project session after restart.
`memory_handle`	No	Reuse the handle returned by a prior project-aware call.
`session_intent`	No	Current durable task intent. A changed value creates an immutable revision.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`error`	No
`query`	No
`memory`	No
`results`	No
`elapsed_ms`	No
`memory_handle`	No
`research_context`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv1.0.2Sep 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max papers (default 10)."New value: +"Maximum papers. Integer 1-10, default 10."

Changed7 schema fields changedv1.0.0Aug 28, 2026

addedInput schema / properties / memory_handle

Added value: +{
+  "description": "Reuse the handle returned by a prior project-aware call.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedInput schema / properties / project_id

Added value: +{
+  "description": "Project memory id.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / session_id

Added value: +{
+  "description": "Stable host task id. Reuses the same project session after restart.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / session_intent

Added value: +{
+  "description": "Current durable task intent. A changed value creates an immutable revision.",
+  "maxLength": 2000,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / memory
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / memory_handle
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / research_context

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "prior_searches": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "query": {
+            "type": "string"
+          },
+          "relation": {
+            "enum": [
+              "same",
+              "related",
+              "recent"
+            ],
+            "type": "string"
+          },
+          "results": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "searched_at": {
+            "type": "string"
+          },
+          "surface": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "query",
+          "relation",
+          "searched_at",
+          "results"
+        ],
+        "type": "object"
+      },
+      "maxItems": 3,
+      "type": "array"
+    }
+  },
+  "required": [
+    "prior_searches"
+  ],
+  "type": "object"
+}

Addedv0.8.0Aug 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already convey readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful behavioral context: provider/fallback behavior, caching with the same TTL as search, a 10-paper cap, and provenance in research mode. However, the write-side behavior is only vaguely referenced through 'orders writes safely', so the side effects are not fully transparent.

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

Conciseness3/5

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

The purpose is front-loaded and many sentences carry value, but the description is somewhat sprawling. The 'one local broker lets multiple MCP sessions query the same knowledge base concurrently and orders writes safely' clause feels tangential, and 'with research enabled' is repeated, making the description less crisp than it could be.

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?

The tool has an output schema and full schema-level parameter descriptions, so return-value documentation is not required. Still, the research-mode behavior is under-specified: the description mentions research_context and provenance but does not explain how to enable research mode or which optional parameters activate it. For a 6-parameter tool with memory/session semantics, this is a notable gap.

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%, so the baseline is 3. The description does not meaningfully enrich parameter semantics: it describes what the tool returns but does not explain how project_id, session_id, memory_handle, or session_intent should be used. It adds no parameter-level guidance beyond what the schema already states.

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 is specific: it states the tool is strictly for paper metadata (authors, venue, year, versions, citation counts) and explicitly contrasts this with discovering or reading paper content. This clearly distinguishes scholar_search from the sibling search tool, so an agent can understand its role without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use rule ('Use only for paper metadata') and an explicit when-not-to-use rule ('Do not use it to discover or read paper content; use search with extract_mode instead'). This is a clear alternative-routing instruction that requires no inference.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/HarimxChoi/google-surf-mcp'

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