zhenzhen-nanobanana-mcp

List Models

list_models

Read-only

Lists available image model families, 2k/4k variants, API formats, directories, and limits to help choose the right model for e-commerce image tasks without network access or API keys.

Instructions

列出三个模型家族及已有2k/4k变体（共7个标识）、API格式、目录与限制；不联网、不返回密钥。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_models"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`models`	Yes
`input_dirs`	Yes	兼容字段，始终为空列表，表示没有目录白名单。
`output_dir`	Yes
`api_formats`	Yes
`async_tasks`	No
`base_models`	No
`capabilities`	No
`default_model`	Yes
`max_batch_items`	Yes
`sync_generation`	No
`concurrency_scope`	No		shared_output_directory
`local_file_access`	Yes
`max_pending_tasks`	No
`upstream_verified`	No
`api_key_configured`	Yes
`default_api_format`	Yes
`supported_endpoints`	No
`max_reference_images`	Yes
`reference_input_note`	No		Gemini/Chat多模态和Generations参考图编码未在本次收费实测；nano-banana-pro仅DALL·E，Edits重复image字段。
`concurrency_per_process`	Yes	兼容字段：本机配置上限；实际按共享输出目录的SQLite账本限制并发。
`max_wait_timeout_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.1Oct 23, 2026

addedOutput schema / properties / base_models

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / max_wait_timeout_seconds

Added value: +{
+  "default": 1200,
+  "type": "integer"
+}

addedOutput schema / properties / sync_generation

Added value: +{
+  "default": true,
+  "type": "boolean"
+}

First observedv0.2.1Oct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds that no keys are returned, which is security-relevant context beyond the annotations, and previews the returned content (identifiers, formats, limits). '不联网' largely restates openWorldHint=false, but the 'no keys returned' and content preview add value.

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?

A single dense sentence, semicolon-delimited, with the verb and main content front-loaded. It packs several facts efficiently, though the semicolon list is slightly dense to parse.

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?

With an output schema present, the description needn't detail return values, but it still summarizes them, and it discloses the non-networking/non-secret constraints. Complete for a zero-parameter catalog tool.

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?

Zero parameters, so the schema baseline is 4. There are no parameter semantics to explain and the description correctly covers none.

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 uses a specific verb + resource (列出/list 模型/models) and quantifies the payload: three families, 2k/4k variants, 7 total identifiers, plus API formats, catalog and limits. This is clearly distinct from the image-task siblings and an agent can tell what it returns without opening the schema.

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?

Usage is implied — an agent would call it to discover available models — but the description never states when to use this vs alternatives or any prerequisites. For a no-param discovery tool this is acceptable but not explicit.

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