Skip to main content
Glama

Codex Imagem

by io.github.mcp-dir

codex_image_generate

Gera uma imagem a partir de um texto, usando a cota de imagens da assinatura ChatGPT conectada (não consome créditos de API). Retorna um link de download do PNG, que também fica na aba Arquivos do mcp.ai. Leva cerca de 1 minuto. A dimensão é escolhida pelo gerador e não pode ser fixada; descreva enquadramento e proporção dentro do próprio prompt (ex.: 'composição horizontal, bem largo'). Uma imagem por chamada.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Extends beyond annotations with meaningful details: quota usage, timing, output link, storage in Files tab, and dimension limitation. No contradiction with annotations; annotations are generic while this adds specific behavioral context.

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?

Three concise sentences, front-loaded with the core action resins. Efficiently packs quota, timing, output, and constraint without fluff.

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?

No output schema, so description carries burden to explain result: download link also in Files tab. Covers quota, timing, dimension limitation scare. Missing explanation of 'account' parameter, but overall sufficient for a simple generation tool.

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

Parameters3/5

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

Schema has 0% description coverage, so description must compensate. It does explain usage of 'prompt' (include framing and aspect ratio) but does not mention 'account' parameter at all. Partial compensation.

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?

Clearly states the verb+resource: generates an image from text. Distinct from sibling 'codex_image_subscription' which handles subscription info. Adds specifics (uses ChatGPT image quota, not API credits) that help differentiate.

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?

Provides clear context: consumes image quota, takes ~1 minute, one image per call. Mentions constraints (dimension cannot be fixed, describe framing in prompt). Does not explicitly name alternatives, but the usage scenario is clear enough.

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

All Codex Imagem toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: authenticate handles login, connect checks status, codex_image_generate creates images, and marketplace is a meta-catalog. There is minor overlap between connect and codex_image_subscription both showing status, but detailed descriptions mitigate confusion. Marketplace is broad but self-contained.

Naming Consistency2/5

Tool names follow mixed conventions: verb-only (authenticate, connect), verb_noun (report_bug, show_version), prefixed with codex_image_ (generate, subscription), and noun-only (marketplace, toolkit_info). No consistent pattern across the set, making it hard to predict tool names.

Tool Count4/5

With 8 tools, the count is within the typical 3-15 range and not excessive. The scope is broad (image generation plus platform utilities), but each tool has a defined role, so the number feels justified for a meta-toolkit server.

Completeness4/5

For the image generation domain, only generate and subscription are present, lacking image history or management features. However, the marketplace tool can dynamically fill gaps by invoking other MCPs, and the core generate workflow is covered. Platform utilities like reporting and versioning are complete.

Resources