Skip to main content
Glama
xumingjun5208

Gemini MCP Server

gemini_chat

Read-only

Send messages to Google Gemini AI for responses, supporting multi-turn conversations, file analysis (text, code, images), and customizable parameters like temperature and output format.

Instructions

Send a message to Google Gemini and get a response.

Args:
    params (GeminiChatInput): Chat parameters including:
        - prompt (str): The prompt to send
        - file (Optional[list[str]]): Files to include (text, code, images)
        - session_id (Optional[str]): Session ID for multi-turn chat, use 'last' for recent
        - model (Optional[str]): Override model selection
        - system_prompt (Optional[str]): System context
        - temperature (Optional[float]): Creativity (0.0-2.0)
        - max_tokens (Optional[int]): Max response length
        - response_format: Output format - 'markdown' or 'json'

Returns:
    str: Response with SESSION_ID for continuation.

Examples:
    - Simple: prompt="What is AI?"
    - With file: prompt="Review", file=["main.py"]
    - With image: prompt="Describe", file=["photo.jpg"]
    - Continue: prompt="Tell me more", session_id="last"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds valuable behavioral context beyond what annotations provide. While annotations indicate read-only and non-destructive operations, the description explains multi-turn chat capabilities with session_id, file handling with glob patterns, and model auto-selection behavior. No contradictions with annotations exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Args, Returns, Examples), uses bullet points for readability, and every sentence adds value. It's appropriately sized for a complex tool with many parameters and provides essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, multi-turn chat, file handling) and the presence of an output schema, the description provides complete context. It explains parameter usage, behavioral characteristics, and includes practical examples, making it fully adequate for an AI agent to understand and use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description comprehensively documents all 8 parameters with clear explanations of their purpose, constraints, and usage patterns. It adds significant value beyond the bare schema by explaining what each parameter does and how to use them effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Send a message to Google Gemini and get a response') with the exact resource (Google Gemini). It distinguishes from the sibling tool gemini_list_models by focusing on chat completion rather than model listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool (for sending messages to Gemini) and includes examples that illustrate different usage scenarios. However, it doesn't explicitly state when NOT to use it or mention the sibling tool as an alternative for different purposes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xumingjun5208/aistudio-gemini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server