agy-image
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_PATH | No | Where to find the binary to extract credentials from, and to run as fallback. | ~/.local/bin/agy |
| AGY_PROJECT | No | Value of the project field. | aicode-consumers |
| AGY_API_HOST | No | Request host. | https://daily-cloudcode-pa.googleapis.com |
| AGY_FALLBACK | No | Set to 0 to disable the agy agent fallback. | 1 |
| AGY_CLIENT_ID | No | Override the OAuth client ID, e.g. if Google rotates it. | read from the agy binary |
| AGY_TOKEN_FILE | No | agy login token file. | ~/.gemini/jetski-standalone-oauth-token |
| AGY_API_TIMEOUT | No | Request timeout, in seconds. | 180 |
| AGY_IMAGE_MODEL | No | Image model. | gemini-3.1-flash-image |
| AGY_QUOTA_STATE | No | Where the last quota info is cached. | ~/.cache/agy-image/quota.json |
| AGY_CLIENT_SECRET | No | Override the OAuth client secret, e.g. if Google rotates it. | read from the agy binary |
| AGY_FALLBACK_TIMEOUT | No | Fallback time limit, in seconds. | 300 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageB | Generate an image using the logged-in Google AI Pro quota (Antigravity), by calling the image generation endpoint directly instead of running the |
| antigravity_statusA | Check Antigravity image-generation configuration & auth status. Only inspects local state (token file, model, host) and makes sure the token can be refreshed — it doesn't call the image endpoint, so it doesn't use any quota. Use this when generate_image fails. |
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 2 tools
The two tools have clearly distinct purposes: generate_image performs generation while antigravity_status only inspects local configuration/auth state and uses no quota. An agent can easily tell which to call, and the description of antigravity_status even directs use after generate_image fails.
generate_image follows a clear verb_noun pattern, while antigravity_status is noun_noun naming a status resource. This is a minor, readable deviation within an otherwise consistent snake_case style.
Two tools is on the thin side for a server, though the scope (quota-backed image generation plus diagnostics) is genuinely narrow. The set just barely covers the domain without feeling under-served, landing at borderline.
The core lifecycle of generating an image and diagnosing failures is covered. Minor gaps exist — no way to inspect remaining quota or explicitly refresh/reconfigure auth beyond the status check — but these are workable around for such a focused server.