Antigravity CLI Use
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkB | Inspect server, CLI, vault, and supported orchestration capabilities. |
| list_accountsB | List accounts without exposing credentials, including cached quota and live worker state. |
| list_modelsC | Discover exact model ids accepted by the installed Antigravity CLI. |
| refresh_account_usageA | Refresh live quota for one or all accounts. Runs as zero-token /usage jobs and can return immediately or wait. |
| submit_jobB | Queue one asynchronous Antigravity task in the caller current workspace. Returns immediately with a job id. |
| submit_batchB | Queue independent tasks for quota-aware parallel execution across distinct accounts. |
| analyze_workflowA | Inspect a DAG before execution: parallel stages, critical-path estimate, redundant edges and file conflicts. Does not run workers or modify files. |
| submit_workflowB | Queue a DAG with critical-path priority and file conflict reservations. Independent tasks with disjoint write_paths run in parallel. Returns analysis and a workflow resource URI. |
| get_workflow_statusB | Get one compact snapshot of the entire workflow, revisions, file blockers and measured timings, without model response bodies. |
| wait_workflowA | Event-driven wait for the entire workflow. Reuse after_revision to suppress old completions. Default 60s; up to 300s only when the client request timeout exceeds wait_ms. Cancellation stops waiting, not workers. |
| get_job_statusA | Get compact state and progress for one job without returning the full response. |
| get_job_resultB | Get a terminal result or long-poll for up to 60 seconds. max_chars controls main-agent token usage. |
| list_jobsC | List recent jobs, optionally filtered by state or workflow. |
| cancel_jobA | Cancel a queued or running job and terminate its complete process tree. |
| continue_jobC | Continue a completed conversation on the same account, preserving session affinity. |
| get_account_usageC | Return locally measured token totals and recent jobs for one account. |
| open_sessionC | Open a verified warm stream-json session on one account for low-latency multi-turn work. |
| session_turnA | Send one prompt to a warm session. The full result is saved locally while max_chars bounds MCP context usage. |
| list_sessionsB | List live warm sessions and their bound accounts. |
| close_sessionA | Gracefully close a warm session, or force-kill its process tree. |
| cli_executeB | Execute any non-interactive Antigravity CLI argv for full CLI coverage. Mutating management commands require allow_mutating=true. |
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 21 tools
Most tools have distinct purposes (e.g., jobs vs sessions vs workflows), but some overlap exists: `get_job_status` and `get_job_result` could be confused, and `refresh_account_usage` vs `get_account_usage` have subtle differences. Descriptions clarify boundaries, but the set is dense with similar-sounding operations.
Predominantly consistent verb_noun pattern (list_jobs, cancel_job, submit_job) with minor deviations like `cli_execute` (noun_verb) and `session_turn` (noun_noun). Still mostly predictable and readable.
21 tools is on the heavy side for a CLI orchestration server, bordering the 16-25 'heavy' range. Some tools feel like thin wrappers (e.g., health_check, list_models), but the domain is broad enough to justify many.
Covers job lifecycle (submit, cancel, status, result), session management (open, turn, close, list), workflow orchestration (analyze, submit, wait, status), and account/model discovery. Minor gaps: no explicit delete or update operations for jobs/workflows, but core workflows are well-covered.