Enables direct collaboration between Claude Code and Gemini AI models through MCP protocol
This server has critical gaps in definition quality. While 4 tools are explicitly registered with input schemas and descriptions, the descriptions lack depth and specificity required for LLM-driven tool selection. No output schemas are documented. Parameters are minimally described. The tool set conflates multiple concerns (ask_gemini doubles as a generic question answerer and code reviewer via prompt engineering). Error messages are generic ('Error calling Gemini'). The server_info tool is a fallback status check, not a production tool. Zero parameter descriptions exceed the 'basic' threshold of 72 chars. No dependency hints, no retry guidance, no actionable error recovery.
Ask Gemini a question and get the response directly in Claude's context
Brainstorm solutions with Gemini, response visible to Claude
Have Gemini review code and return feedback directly to Claude
Get server status and error information
No output schemas documented. LLMs cannot plan downstream actions or extract structured data from responses.
ask_gemini lacks specificity and conflates multiple intents (Q&A, reasoning, code review). Tool names should map 1:1 to user intents, not be multipurpose pass-throughs.
Parameter descriptions are minimal (8-25 chars). Descriptions do not explain constraints, formats, or expected ranges.
Error handling returns raw API errors ('Error calling Gemini: {str(e)}') with no recovery guidance. Per pattern, errors should guide LLM on retry vs. user-fixable vs. fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | F | 11 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 45 | 2024-11-05+ | v1 |
Tool descriptions (50-120 chars) are below baseline (194 chars). They lack WHEN to use, dependency hints, or guidance on tool selection vs. alternatives.
temperature parameter has no constraints documented (0.0-1.0 range is in description, but NOT in schema minimum/maximum). LLM may pass invalid values.
server_info is a status/debugging tool, not a production tool. Its presence suggests server design prioritizes debugging over user value.
No output field documentation. Responses are raw text strings ('GEMINI RESPONSE:\n\n{result}'). LLM cannot extract structured data, relate it to downstream tools, or validate completeness.