NanoBanana MCP

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.1.1
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: conversation management (clear_conversation), chat (gemini_chat), image generation (gemini_generate_image), image editing (gemini_edit_image), history retrieval (get_image_history), aspect ratio configuration (set_aspect_ratio), and model selection (set_model). The boundaries between tools are well-defined and unambiguous.
Naming Consistency4/5
The naming follows a mostly consistent pattern with six tools using snake_case and clear action-object naming (clear_conversation, get_image_history, set_aspect_ratio, set_model). The three gemini_* tools deviate slightly by prefixing with 'gemini_' but maintain internal consistency. The main inconsistency is that gemini_chat doesn't follow the verb_noun pattern as strictly as others.
Tool Count5/5
Seven tools is an ideal number for this Gemini interaction server, covering core functionality without bloat. Each tool serves a distinct purpose in the workflow: conversation management, chat interaction, image generation/editing, history access, and session configuration. No tool feels redundant or unnecessary for the server's scope.
Completeness4/5
The tool surface provides excellent coverage for Gemini-based chat and image workflows, including conversation management, multi-modal chat, image generation/editing, and session configuration. The only minor gap is the lack of a tool to manage multiple conversations or sessions beyond the current one, but agents can work effectively with the provided tools for most use cases.
Average 3.4/5 across 7 of 7 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'clears' conversation history, implying a destructive mutation, but doesn't specify whether this is permanent/reversible, requires specific permissions, affects other data, or has side effects (e.g., notifications). For a destructive tool with zero annotation coverage, this leaves critical behavioral traits undisclosed.
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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'clear' entails (e.g., deletion, archiving), what happens on success/failure, or return values. For a tool that permanently modifies data, more context is needed to use it safely and effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the single parameter 'conversation_id' documented as 'The conversation ID to clear'. The description adds no additional meaning beyond this, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('clear') and resource ('conversation history for a specific conversation ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (like 'gemini_chat' or 'get_image_history'), which appear to be related to chat/image functionality but aren't directly comparable deletion alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the conversation must exist), exclusions (e.g., cannot clear active conversations), or related tools (like 'gemini_chat' for creating conversations). The agent must infer usage from context alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions multi-turn conversations and image limits (max 10), which are useful, but lacks critical details like rate limits, authentication needs, response format, or error handling. This is inadequate for a chat tool with potential complexity.
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 a single, efficient sentence that front-loads the core purpose and key features (multi-turn, image support). Every word earns its place with no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a chat tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on response format, error cases, rate limits, and how it integrates with siblings like clear_conversation or get_image_history. More context is needed for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional meaning about parameters beyond implying image support aligns with the 'images' parameter. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Chat with') and target ('Gemini 3.1 Flash model'), and mentions multi-turn conversations and image support. However, it doesn't explicitly differentiate from siblings like gemini_edit_image or gemini_generate_image, which also interact with Gemini but for different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions multi-turn conversations and image support, which implies usage for interactive chat with visual inputs. However, it provides no explicit guidance on when to use this tool versus alternatives like gemini_edit_image or set_model, nor does it mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get the list') but does not specify permissions, rate limits, pagination, or what 'session' entails. This is inadequate for a tool that likely interacts with session data, leaving key behavioral traits undisclosed.
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 a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded and appropriately sized, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It does not explain what the returned list contains (e.g., image metadata, URLs), how it's structured, or any error conditions. For a tool that retrieves historical data, this leaves significant gaps in understanding its full context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the parameter 'conversation_id' documented as 'The session ID to get image history for'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get the list') and resource ('generated/edited images in a session'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'gemini_generate_image' or 'gemini_edit_image', which might handle similar image-related operations but with different functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as how it relates to sibling tools like 'gemini_generate_image' or 'clear_conversation'. It mentions 'for reference' but lacks explicit context, prerequisites, or exclusions, leaving usage unclear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'supports session history references' and 'image consistency features,' which adds useful context about how it interacts with session state. However, it doesn't disclose critical behavioral traits like whether edits are destructive to the original image, authentication requirements, rate limits, error conditions, or what happens when output_path isn't provided (beyond the schema's description). The description adds some value but leaves significant gaps for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose ('Edit or modify existing images based on prompts') and adds two key features. There's no wasted verbiage, and every clause adds value. It could be slightly more structured by separating core purpose from features, but it's appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (7 parameters, mutation operation, no annotations, no output schema), the description is moderately complete. It covers the core purpose and hints at session integration, but it lacks details on behavioral outcomes, error handling, or what the tool returns. Without annotations or output schema, the description should do more to explain the mutation's effects and results, but it provides a basic foundation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description doesn't add any parameter-specific semantics beyond what's already in the schema (e.g., it doesn't explain how 'edit_prompt' interacts with 'reference_images' or clarify the 'conversation_id' usage). With high schema coverage, the baseline is 3, and the description doesn't compensate with additional insights.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as editing or modifying existing images based on prompts, which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'gemini_generate_image' (which likely creates new images) or 'get_image_history' (which retrieves but doesn't edit). The description mentions session history references and image consistency features, which adds specificity but not explicit sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context through mentions of session history references ('last' or 'history:N') and image consistency features, suggesting this tool is for iterative editing within a session. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'gemini_generate_image' for new images or 'clear_conversation' for session management. No when-not-to-use scenarios or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it's a generation tool (implying creation/mutation), supports session-based consistency, and mentions style/character maintenance. However, it lacks details on permissions, rate limits, error handling, or output format (e.g., image type, size). The description doesn't contradict annotations, but it's incomplete for a tool with multiple parameters and no output schema.
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 concise and front-loaded: the first sentence states the core purpose, and the second adds key functionality (session-based consistency). Both sentences earn their place by providing essential information without redundancy or fluff, making it easy to scan and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (7 parameters, no annotations, no output schema), the description is moderately complete. It covers the main purpose and a key feature (session consistency) but lacks details on behavioral aspects like mutation effects, error cases, or output handling. Without annotations or output schema, the description should do more to compensate, but it provides a basic foundation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 7 parameters. The description adds minimal value beyond the schema: it mentions 'session-based image consistency,' which relates to 'conversation_id' and 'use_image_history,' but doesn't provide additional syntax or usage details. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Generate images using Gemini's image generation capabilities.' It specifies the action (generate) and resource (images) with the technology (Gemini). However, it doesn't explicitly differentiate from sibling tools like 'gemini_edit_image' or 'get_image_history' beyond mentioning session-based consistency.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context through 'session-based image consistency for maintaining style/character across multiple generations,' suggesting this tool is for generating new images with optional consistency features. It doesn't provide explicit guidance on when to use this versus alternatives like 'gemini_edit_image' or 'set_aspect_ratio,' nor does it mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that this affects session configuration and mentions default behavior, but doesn't cover important behavioral aspects like whether this persists across sessions, requires specific permissions, or has rate limits.
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?
Two sentences with zero waste - the first states the purpose, the second provides usage guidance. Every word earns its place, and the information is front-loaded appropriately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a configuration tool with 2 parameters and 100% schema coverage but no annotations or output schema, the description is reasonably complete. It explains what the tool does and provides practical guidance, though it could benefit from more behavioral context given the absence of annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents both parameters. The description adds minimal value beyond the schema by mentioning the performance characteristics of each model option, but doesn't provide additional parameter semantics.
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 ('Set') and resource ('Gemini model for this session'), distinguishing it from siblings like gemini_chat or set_aspect_ratio. It specifies the exact configuration being modified.
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 about when to use each option ('flash' for faster generation, 'pro' for higher quality) and indicates the default. However, it doesn't explicitly state when NOT to use this tool or mention alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses that this is a session-level configuration tool that affects subsequent operations, which is valuable behavioral context. However, it doesn't mention whether this setting persists across sessions, what happens if called multiple times, or any error conditions beyond the temporal requirement.
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 uses only two sentences that are completely focused and front-loaded. The first sentence states the purpose, the second provides critical usage guidance. There is zero wasted text or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a configuration tool with 2 parameters and 100% schema coverage but no annotations or output schema, the description provides good context about when and why to use it. It could be more complete by addressing persistence across sessions or error conditions, but it covers the essential operational context adequately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. This meets the baseline expectation when schema coverage is complete.
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 ('Set the aspect ratio') and the target ('for subsequent image generation and editing in this session'). It distinguishes this tool from siblings like gemini_generate_image or gemini_edit_image by focusing on configuration rather than creation/modification.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('Must be called before generating/editing images if a specific ratio is desired') and implies alternatives (using default ratios if not called). This provides clear temporal and conditional guidance for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![nanobanana-mcp MCP server](https://glama.ai/mcp/servers/pistachiomatt/nanobanana-mcp/badges/card.svg)](https://glama.ai/mcp/servers/pistachiomatt/nanobanana-mcp)

Score Badge

Copy to your README.md:

[![nanobanana-mcp MCP server](https://glama.ai/mcp/servers/pistachiomatt/nanobanana-mcp/badges/score.svg)](https://glama.ai/mcp/servers/pistachiomatt/nanobanana-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/pistachiomatt/nanobanana-mcp'

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