sub-antigravity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUB_ANTIGRAVITY_AGY_PATH | No | Path to the agy executable. If not specified, sub-antigravity searches the current PATH and common Windows installation locations. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| antigravity_delegateA | Start a delegated Antigravity job and return immediately with a job ID. Give one complete goal with constraints and expected completion evidence. Pass a previous conversation_id to continue that Antigravity conversation. Enable edits only when authorized. |
| antigravity_jobA | Wait for, inspect, retrieve, or cancel a delegated Antigravity job. Prefer action=wait and detail=compact. Request detail=full only when the user needs the complete AGY response because full tool results consume the host model's context. |
| antigravity_checkC | Check AGY discovery, local login-visible models, and the selected Gemini model. |
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 3 tools
Each tool has a clearly distinct role: delegate starts a job, job manages a running or completed job, and check inspects environment configuration. There is no meaningful overlap in purpose.
All tools share the antigravity_ prefix and use snake_case, but antigravity_job breaks the verb-led pattern established by antigravity_delegate and antigravity_check. The convention is still readable and predictable.
Three tools is a well-scoped set for a delegated job system: start, manage, and check environment. Each tool earns its place without unnecessary redundancy.
The core lifecycle of starting, waiting on, retrieving, and canceling delegated jobs is covered, along with environment discovery. A list-all-jobs operation is absent but is not clearly required for the server's stated purpose.