Gemini Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | API key for Google Gemini API |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Gemini 2.0とGoogle検索を使用して、最新の情報に基づいた回答を生成 |
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
Only one tool exists, so there is no possibility of ambiguous selection. An agent will always know the purpose of the only tool.
The single tool 'search' uses a clear, simple verb name. With only one tool, there are no naming pattern inconsistencies to evaluate.
With just one tool, the server feels very thin. While the narrow purpose of search may justify a minimal surface, it is at the borderline of being too few tools for a coherent toolkit, so a score of 3 is appropriate.
The server's stated purpose is to generate answers using Gemini and Google search. The single 'search' tool fully covers this operation; there are no obvious missing functions within the given scope.