Gemini Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_BRIDGE_TIMEOUT | No | Timeout in seconds for Gemini CLI operations (default: 60, range: any positive integer). Can be overridden per tool call. | 60 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| consult_geminiB | Send a query directly to the Gemini CLI. Args:
query: Prompt text forwarded verbatim to the CLI.
directory: Working directory used for command execution.
model: Optional model alias ( Returns: Gemini's response text or an explanatory error string. |
| consult_gemini_with_filesA | Send a query to the Gemini CLI with file context. Args:
query: Prompt text forwarded to the CLI.
directory: Working directory used for resolving relative file paths.
files: Relative or absolute file paths to include alongside the prompt.
model: Optional model alias ( Returns: Gemini's response or an explanatory error string with any warnings. |
| web_searchA | Ask Gemini queries with web search context. Note: This uses Gemini CLI's automatic web search capability. The model determines when to search based on query context. Best-effort web search - not guaranteed for every query. Args: query: Search query or question to look up on the web directory: Working directory for command execution model: Optional model alias (flash, pro, or custom) timeout_seconds: Optional per-call timeout override in seconds Returns: Gemini's response with potential web sources |
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 3 tools
Each tool has a clearly distinct purpose: consult_gemini for plain queries, consult_gemini_with_files for queries with file context, and web_search for web-augmented queries. No functional overlap.
Naming mostly follows a verb_noun pattern with 'consult_gemini' as a base, but 'web_search' deviates by not starting with 'consult'. Overall pattern is still predictable and readable.
Three tools is an appropriate scope for a Gemini CLI bridge, covering the essential query modes (plain, with files, web search) without unnecessary bloat.
The set covers the primary use cases for interacting with Gemini. Missing tools for model listing or configuration, but these are minor gaps for the intended purpose of querying.