GPT Image Studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Your OpenAI API key. This can alternatively be provided in config.json instead of the environment variable. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image with OpenAI gpt-image-2.5 using the user's own API key; saves it locally and returns the file paths and cost. Without a requested spec use 2K 16:9 + high (about $0.06). 4K, xhigh, max or several images cost more — tell the user the rough cost first. Always tell the user what each run cost. |
| check_connectionA | Check that the API key and network work (free). |
| get_spendingA | Get spending today / this month / total and the estimated remaining balance. |
| sync_balanceA | When the user says '同步余额' or 'sync my balance', start with {}. Follow the returned browser instructions, then call again with all four fields. Report success only when the result says synced. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
generate_image is clearly distinct from the account and cost utilities. check_connection, get_spending, and sync_balance all touch account/cost state, but their descriptions provide enough boundaries; sync_balance and get_spending could still be confused at first glance.
All four tools use a consistent snake_case verb_noun pattern: sync_balance, check_connection, generate_image, get_spending. The convention is predictable and easy to scan.
Four tools is well-scoped for a focused image-generation studio: generate, verify connectivity, inspect spending, and sync balance. Each tool has a clear role without unnecessary surface area.
The core lifecycle is covered: connection check, image generation, cost reporting, and balance syncing. Minor gaps exist around managing or listing previously generated images, but the returned file paths let agents work around that.