gemini-bridge
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
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_geminiA | Send a query directly to the Gemini CLI. |
| consult_gemini_with_filesA | Send a query to the Gemini CLI with file context. |
| web_searchA | Ask Gemini queries with web search context. |
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: plain query, query with file context, and web search. There is no overlap or ambiguity between them.
Two tools share the 'consult_gemini' prefix with suffixes, but 'web_search' breaks the pattern. The naming is mostly consistent but has a minor deviation.
With 3 tools, the set is lean and well-scoped for a Gemini CLI bridge. Each tool adds essential functionality without redundancy.
Core interactions (simple query, file-augmented, web search) are covered. Missing features like streaming or tool execution are non-critical for this server's scope.