gemini-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_MODEL | No | Gemini model to use. | gemini-2.5-flash |
| GEMINI_API_KEY | No | Google AI Studio API key. Required unless using Vertex AI. | |
| GEMINI_PROVIDER | No | Set to `vertex` to use Vertex AI. | |
| VERTEX_LOCATION | No | Vertex AI location. | us-central1 |
| GEMINI_TIMEOUT_MS | No | Request timeout in milliseconds. | 60000 |
| VERTEX_PROJECT_ID | No | GCP project ID. Required when `GEMINI_PROVIDER=vertex`. | |
| RESOLVE_SOURCE_URLS | No | Replace Google grounding redirect links with the real page URLs (reads only the redirect header, 3s timeout per link). Set to `false` to skip. | true |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchA | Searches the web with Google Search (via Gemini grounding) and returns a summarized answer with inline citations [n] and a list of source URLs. Use it for up-to-date information or facts not in your training data. |
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
There is only one tool, so there is no possibility of misselection between tools. Its purpose (web search with summarized answers and citations) is stated unambiguously.
The single name google_search is a clear, lowercase snake_case noun-qualified action name with no competing conventions to clash with. There is nothing inconsistent to evaluate.
One tool is thin compared to the typical 3-15 range, but it exactly matches the server's narrow, single-purpose scope (Gemini-grounded Google search), so nothing is bloat or missing at the count level.
The search-and-summarize workflow is fully covered with inline citations and source URLs, which is the whole stated domain. Minor gaps exist (no way to fetch/open a full page for deeper reading, no query options like date range or news/image scopes) that an agent could work around by re-searching.