antigravity-desktop-live-quota-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_THRESHOLD_LOW | No | Sarı gösterge eşik yüzdesi (> %20, altı kırmızı) | 20 |
| AGY_THRESHOLD_HIGH | No | Yeşil gösterge eşik yüzdesi (> %50) | 50 |
| AGY_BROWSER_FETCH_MS | No | Tarayıcı JS döngüsünün yerel kota sorgulama periyodu (milisaniye) | 30000 |
| AGY_WATCHER_CHECK_SEC | No | Lider sürecin pencere varlığını ve rozet durumunu denetleme sıklığı (saniye) | 8 |
| AGY_ENABLE_PULSE_ALERT | No | Nabız animasyonunu etkinleştirme bayrağı | true |
| AGY_PULSE_ALERT_THRESHOLD_PCT | No | Kritik kota kırmızı nabız animasyonu eşiği (≤ %15) | 15 |
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 |
|---|---|
| get_quota_statusB | Antigravity yerel language_server üzerinden canlı AI model kota ve kullanım durumunu (Gemini 5h/weekly, Claude/GPT, Argon) sorgular. |
| reinject_badgeC | Antigravity Desktop penceresinin üst menü çubuğuna canlı kota göstergesini (rozetini) anında yeniden enjekte eder ve tazeler. |
| get_instance_statusB | Çalışan MCP sunucusunun PID, çoklu-örnek liderlik (Leader/Standby) ve kilit durumu bilgilerini döndürür. |
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 targets a clearly distinct object: quota data (get_quota_status), the UI badge element (reinject_badge), and the server process itself (get_instance_status). There is no plausible way to confuse one for another.
All three names are snake_case verb_noun constructions (get_*, reinject_*), and the nouns map directly to the resource being acted on. Minor variation in verb choice (reinject vs get) is semantically meaningful, not inconsistent.
Three tools is on the thin side, but this is a narrow single-purpose server (live quota monitoring for a desktop app) and each tool covers a genuinely separate concern. Nothing is redundant or filler.
The surface covers querying quota, refreshing the badge, and inspecting instance leadership, but the badge lifecycle is one-directional — there is no way to hide/disable the badge or configure its refresh behavior, and no tool to reset or re-acquire leadership. These are notable gaps an agent would hit when trying to fully manage the display state.