Skip to main content
Glama
Sign In
Nano Banana MCP Server

Nano Banana MCP Server

by plemio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Maintenance and cleanup operations

maintenance
Read-only

Run cleanup operations to remove expired Files API entries, clean old local files, check storage quota, and fix database inconsistencies. Preview changes with dry-run before applying.

Instructions

Perform maintenance operations following workflows.md patterns.

Available operations:

  • cleanup_expired: Remove expired Files API entries from database

  • cleanup_local: Clean old local files based on age/LRU

  • check_quota: Check Files API storage usage vs. ~20GB budget

  • database_hygiene: Clean up database inconsistencies

  • full_cleanup: Run all cleanup operations in sequence

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, only report what would be done without making changes
operationYesMaintenance operation to perform: 'cleanup_expired', 'cleanup_local', 'check_quota', 'database_hygiene', 'full_cleanup'
keep_countNoFor local cleanup: minimum number of recent files to keep
max_age_hoursNoFor local cleanup: maximum age in hours (default: 168 = 1 week)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior1/5

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

Description directly contradicts readOnlyHint=true. Operations like 'Remove expired Files API entries from database' and 'Clean old local files' imply mutation, yet annotations declare the tool read-only. Also lacks disclosure of side effects, permissions, or reversibility.

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?

Very concise: one introductory line plus a clean bullet list of operations. Front-loads the tool purpose and uses scannable format with no 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?

Complex tool with 4 parameters and 5 operation variants, yet the description lacks guidance on parameter applicability (e.g., keep_count and max_age_hours only for cleanup_local) and return behavior. The readOnlyHint contradiction further reduces completeness.

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

Parameters4/5

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

Schema provides 100% parameter descriptions, but the tool description adds semantic detail for the operation parameter by explaining what each operation does (e.g., 'check_quota: Check Files API storage usage vs. ~20GB budget'). This goes beyond the schema's repetitive value list.

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?

Purpose is explicit: maintenance and cleanup operations. The description lists five distinct operations with concrete effects (e.g., 'Remove expired Files API entries from database'), distinguishing it from unrelated siblings like generate_image and upload_file.

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?

Although no explicit 'use when' statement is given, the operation list clearly implies the tool is for maintenance/cleanup tasks, and the sibling tools are unrelated (image generation, upload, stats). Missing explicit exclusions or alternative routing, but context is adequate.

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

Deploy Server

Other Tools