Skip to main content
Glama
Sign In
Nano-Banana MCP Server

Nano-Banana MCP Server

by fjacquet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_last_image_info

Retrieve details for the last generated or edited image in this session to inspect metadata and verify results.

Instructions

Get information about the last generated/edited image in this session.

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": "get_last_image_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it only conveys that this is a read of the most recent image. It does not say what happens when no image exists yet (error vs. empty response), nor what fields the returned 'information' contains — significant because there is no output schema to fall back on.

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?

A single front-loaded sentence with no filler; the scope qualifier ('last generated/edited... in this session') appears immediately after the verb. Nothing is wasted.

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?

The tool is simple (no params, no nested objects), but with no annotations and no output schema, the description should have disclosed the shape of the returned information and the no-image-yet behavior. As written it covers the 'what' but not the 'what comes back' or the failure mode.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and it correctly signals that the call is implicitly scoped to the session's last image rather than requiring an ID argument.

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 names a specific verb ('Get information about') and a precisely scoped resource ('the last generated/edited image in this session'), which is clearly distinct from siblings like generate_image, edit_image, and get_configuration_status. It stops short of explicitly naming an alternative tool it must not be confused with, so it lands at a clear-but-undifferentiated 4.

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 phrase 'in this session' implies a precondition (an image must already have been generated or edited) and hints that this is a follow-up query rather than a generation action, but there is no explicit when-to-use/when-not-to-use statement and no pointer to continue_editing or edit_image as alternatives for acting on that image.

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