G-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 |
|---|---|
| searchC | Search on Google for multiple keywords and return the results |
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, making disambiguation perfect. The single tool has a clear and distinct purpose without any ambiguity.
With only one tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'search' follows a simple verb pattern, which is appropriate for its function.
A single tool is too few for a search server, as it lacks basic operations like refining searches, handling different result types, or managing search history. This minimal set feels thin and incomplete for the apparent scope of a search service.
The tool set is severely incomplete for a search domain, offering only a basic search function without any support for advanced features like filtering, pagination, or accessing specific result details. This will likely cause agent failures when more complex search tasks are required.