Skip to main content
Glama

get_configuration_status

Check if the Gemini API token is properly configured for the Nano-Banana-MCP server to ensure integration readiness.

Instructions

Check if Gemini API token is configured

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that checks the Gemini API configuration status and returns a detailed text response indicating if it's configured, the source, and setup instructions if not.
      private async getConfigurationStatus(): Promise<CallToolResult> {
        const isConfigured = this.config !== null && this.genAI !== null;
        
        let statusText: string;
        let sourceInfo = "";
        
        if (isConfigured) {
          statusText = "āœ… Gemini API token is configured and ready to use";
          
          switch (this.configSource) {
            case 'environment':
              sourceInfo = "\nšŸ“ Source: Environment variable (GEMINI_API_KEY)\nšŸ’” This is the most secure configuration method.";
              break;
            case 'config_file':
              sourceInfo = "\nšŸ“ Source: Local configuration file (.nano-banana-config.json)\nšŸ’” Consider using environment variables for better security.";
              break;
          }
        } else {
          statusText = "āŒ Gemini API token is not configured";
          sourceInfo = `
    
    šŸ“ Configuration options (in priority order):
    1. šŸ„‡ MCP client environment variables (Recommended)
    2. 🄈 System environment variable: GEMINI_API_KEY  
    3. šŸ„‰ Use configure_gemini_token tool
    
    šŸ’” For the most secure setup, add this to your MCP configuration:
    "env": { "GEMINI_API_KEY": "your-api-key-here" }`;
        }
        
        return {
          content: [
            {
              type: "text",
              text: statusText + sourceInfo,
            },
          ],
        };
      }
  • src/index.ts:110-118 (registration)
    Tool registration in the ListTools handler, including name, description, and input schema (empty object).
    {
      name: "get_configuration_status",
      description: "Check if Gemini API token is configured",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false,
      },
    },
  • src/index.ts:165-166 (registration)
    Dispatch case in the CallTool request handler that routes to the getConfigurationStatus method.
    case "get_configuration_status":
      return await this.getConfigurationStatus();
  • Input schema definition for the tool: an empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
      additionalProperties: false,
    },
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 states what the tool does but doesn't describe what 'check' entails - whether it returns a simple boolean, detailed status information, error messages if unconfigured, or any side effects. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

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 tool has no annotations and no output schema, the description should provide more complete context about what the check returns and how to interpret results. As a configuration status tool, users need to know what format the status information comes in and what actions to take based on the result, but this is missing.

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 has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and it doesn't need to compensate for any schema gaps.

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 with a specific verb ('Check') and resource ('Gemini API token configuration'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'configure_gemini_token' beyond the obvious check vs. configure distinction.

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 (like needing to run this before using other tools), nor does it suggest when to use 'configure_gemini_token' instead. The usage context is implied but not stated.

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/ConechoAI/Nano-Banana-MCP'

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