GemForge-Gemini-Tools-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Google Gemini API key | |
| DEFAULT_MODEL_ID | No | Default Gemini model ID to use | gemini-2.5-flash-preview-04-17 |
| GEMINI_PAID_TIER | No | Set to 'true' if using paid tier (for rate limits) | false |
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 |
|---|---|
| gemini_searchA | Generates responses based on the latest information using Gemini 2.0 Flash and Google Search. Best for general knowledge questions, fact-checking, and information retrieval. |
| gemini_reasonA | Solves complex problems with step-by-step reasoning using Gemini 2.0 Flash Thinking. Best for math and science problems, coding challenges, and tasks requiring transparent reasoning process. |
| gemini_codeC | Analyzes codebases using Repomix and Gemini 2.5 Pro. Answers questions about code structure, logic, and potential improvements. |
| gemini_fileopsA | Performs efficient operations on files (text, PDF, images, etc.) using appropriate Gemini models (Flash-Lite or 1.5 Pro for large files). Use for summarization, extraction, or basic analysis. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: gemini_code analyzes codebases, gemini_fileops handles file operations, gemini_reason solves complex problems with reasoning, and gemini_search retrieves general information. The descriptions clearly differentiate their domains and use cases, making misselection unlikely.
All tool names follow a consistent 'gemini_' prefix pattern with descriptive suffixes (code, fileops, reason, search). This uniform naming convention makes the tool set predictable and easy to understand, with no deviations in style or structure.
Four tools is a reasonable number for a Gemini-focused server, covering key areas like code analysis, file operations, reasoning, and search. It feels slightly thin but well-scoped, as each tool addresses a distinct domain without unnecessary duplication.
The tool set covers major use cases for Gemini models: code analysis, file handling, reasoning, and information retrieval. Minor gaps might include more specialized operations like image generation or multimodal analysis, but the core functionalities are well-represented for general-purpose tasks.