MCP Google Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMARTSEARCH_AK | Yes | Your access key for Google Custom Search | |
| SMARTSEARCH_ENDPOINT | Yes | Your endpoint for Google Custom Search |
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 |
|---|---|
| searchC | Perform a web search query |
| read_webpageA | Fetch and extract text content from a webpage |
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 2 tools
The two tools have clearly distinct purposes: one fetches content from a specific webpage, while the other performs general web searches. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun pattern (read_webpage, search), with no deviations or mixed conventions. The naming is straightforward and predictable across the set.
With only 2 tools, the server feels thin for a 'Google Server' domain, which typically involves more operations like email, calendar, or document management. This minimal set may not cover the expected scope adequately.
For a server named 'Google Server', there are significant gaps in coverage, such as missing tools for Gmail, Google Drive, Calendar, or authentication. The current tools only handle basic web interactions, leaving core Google services unaddressed.