Skip to main content
Glama

get_image_config_info

Retrieve available configuration options for image generation and editing, including aspect ratios and transformation settings.

Instructions

이미지 생성/편집에 사용 가능한 설정 옵션 정보를 반환합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getConfigInfo() function that implements the actual logic for get_image_config_info tool. Returns configuration object with valid aspect ratios, image sizes, models, and documentation link.
    export function getConfigInfo() {
      return {
        aspectRatios: VALID_ASPECT_RATIOS,
        imageSizes: VALID_IMAGE_SIZES,
        models: {
          default: DEFAULT_MODEL,
          fallback: FALLBACK_MODEL,
          notes: "4K는 pro 모델에서만 지원됩니다.",
        },
        docs: "https://ai.google.dev/gemini-api/docs/image-generation?hl=ko",
      };
    }
  • server.js:279-293 (registration)
    Registration of the get_image_config_info MCP tool. The tool has no input parameters and calls getConfigInfo() to return configuration information as JSON.
    server.tool(
      "get_image_config_info",
      "이미지 생성/편집에 사용 가능한 설정 옵션 정보를 반환합니다",
      async () => {
        const info = getConfigInfo();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(info, null, 2),
            },
          ],
        };
      }
    );
  • Schema definitions for valid configuration options - VALID_ASPECT_RATIOS and VALID_IMAGE_SIZES arrays that are returned by getConfigInfo().
    const VALID_ASPECT_RATIOS = [
      "1:1",
      "2:3",
      "3:2",
      "3:4",
      "4:3",
      "4:5",
      "5:4",
      "9:16",
      "16:9",
      "21:9",
    ];
    const VALID_IMAGE_SIZES = ["1K", "2K", "4K"];
  • Default and fallback model constants (DEFAULT_MODEL and FALLBACK_MODEL) used in the configuration info returned by getConfigInfo().
    const DEFAULT_MODEL = "gemini-3-pro-image-preview";
    const FALLBACK_MODEL = "gemini-2.5-flash-image";
Behavior2/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 states the tool returns information, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 in Korean that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, with every word earning its place.

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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on behavioral context, output format, or usage scenarios. For a simple info-retrieval tool, it meets the bare minimum but could be more complete.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's acceptable given the lack of parameters. A baseline of 4 is appropriate as the schema fully covers the parameter situation.

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: '이미지 생성/편집에 사용 가능한 설정 옵션 정보를 반환합니다' (Returns information about configuration options available for image generation/editing). It specifies the verb ('반환합니다' - returns) and resource ('설정 옵션 정보' - configuration option information), though it doesn't explicitly differentiate from sibling tools like 'generate_image' or 'edit_image'.

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, timing, or relationships with sibling tools such as 'generate_image', 'edit_image', 'start_image_session', or 'continue_image_session'. The agent must infer usage from the purpose alone.

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/jk7g14/gemini-image-mcp'

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