Enhanced Google Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web using Google with enhanced anonymization and anti-detection features. Supports advanced filtering options. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined as web searching with specific features.
Since there is only one tool named 'search', it inherently follows a consistent pattern with itself. There are no deviations or mixing of conventions to evaluate, making it perfectly consistent.
A single tool for an 'Enhanced Google Search MCP' feels too minimal for the apparent scope, as web searching often involves related operations like refining queries or handling results. This thin surface may limit agent capabilities in this domain.
The tool surface is severely incomplete for web searching; it only offers a basic search function without supporting operations such as filtering results, pagination, or accessing cached pages. This creates significant gaps that could lead to agent failures in complex tasks.