Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOCAL_GPU_PROFILENoHardware preset for local GPU inference. Valid values: 8gb_vram, 12gb_vram, 24gb_vram_or_mac_unified.
LOCAL_LLM_BASE_URLNoBase URL for the local OpenAI-compatible LLM server (e.g., http://127.0.0.1:11434/v1 for Ollama).
LOCAL_OLLAMA_MODELNoModel name to use with Ollama for local GPU inference (e.g., qwen2.5-coder:14b).
AGY_GIT_REPORT_ONLYNoSet to 1 to restrict git operations to read-only reporting.
AGY_MAX_CONCURRENCYNoMaximum number of concurrent Antigravity (cloud) subagent tasks. Default is 1.1
AGY_NO_SELF_BOOTSTRAPNoSet to 1 to prevent the server from automatically bootstrapping configuration (e.g., modifying .mcp.json).
LOCAL_GPU_CONCURRENCYNoMaximum number of concurrent local GPU tasks. Default is 1.1
AGY_DENY_SKIP_PERMISSIONSNoSet to 1 to disallow skipping permission checks.

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
codex_researchA

Run read-only research through a dedicated headless Codex CLI. Separate serialized queue from agy. No automatic provider/model fallback. Returns exact model/effort, session, usage when available, and retained job evidence.

codex_followupA

Continue an explicit completed Spillway Codex session in the same workspace/home and model. Always read-only; never resumes the latest ambient session.

codex_job_resultB

Inspect or wait for a Codex job, including retained output and stop evidence.

codex_statusA

Codex setup, queue, model and quota status. Quota is unknown; this does not perform inference.

codex_cancelA

Cancel a queued or running Codex job. Waits for process-stop evidence; an unconfirmed stop quarantines execution.

agy_delegate_researchA

Delegate deep read-only codebase research, cross-module architectural analysis, bug root-cause tracing, or security verification to Google Antigravity CLI (agy) using verified Gemini 3.8 Flash or Gemini 4 Argon models in --mode=plan. SERIALIZATION & ASYNC BUDGET: Calls are serialized (one at a time, AGY_MAX_CONCURRENCY = 1); a prompt that needs more than ~8 minutes of agent time should be split into one bounded question per call, or launched expecting to fetch the result by job_id via agy_job_result (soft handoff at 540s, hard watchdog at AGY_RUN_MAX_MS, cancellable via agy_cancel). WHEN TO USE: Complex multi-file reasoning or architectural audits across 5–30+ files after initial scouting. DO NOT USE FOR: Simple signature, import, or line-number extraction on known files (use local_file_scout instead at 0x quota) or parallel disjoint directory scans (use agy_spawn_swarm instead). RETURNS: Markdown analysis with : citations (or an async job_id handle if still running at soft budget) and telemetry footer.

agy_spawn_swarmA

Dispatch multiple read-only Antigravity subagents using gemini-3.8-flash-low or gemini-3.8-flash-medium across strictly disjoint directory partitions. SERIALIZATION & ASYNC BUDGET: Tasks run sequentially one after another (one at a time, AGY_MAX_CONCURRENCY = 1) and share the same ~8-minute soft budget ceiling; keep each task prompt bounded or fetch any in-flight task result by job_id via agy_job_result. WHEN TO USE: Exploring multiple independent subsystems or directories in a single turn. DO NOT USE FOR: Single-directory research (use agy_delegate_research), single-file signature extraction (use local_file_scout), or overlapping directory paths (rejected by partition validator). RETURNS: Aggregated markdown report per subagent task (or async job_id handles for tasks still running at soft budget) plus telemetry footer.

agy_delegate_editA

Delegate complex multi-file code modifications or cross-module refactoring to Antigravity (agy) in --mode=accept-edits. SERIALIZATION & ASYNC BUDGET: Calls are serialized (one at a time, AGY_MAX_CONCURRENCY = 1); split edits needing >~8 minutes into smaller scoped calls or fetch in-flight runs via agy_job_result. WHEN TO USE: Coordinated edits across multiple existing files requiring Gemini Argon/Flash reasoning. DO NOT USE FOR: Generating a single standalone boilerplate, DTO, schema, or unit test file (use local_draft_leaf_code instead at 0x quota), read-only analysis (use agy_delegate_research), or running test suites (use local_exec_and_triage). RETURNS: Edit summary, optional IDE visual diff confirmation, and telemetry footer.

agy_session_followupA

Resume an existing Antigravity conversation ID (--conversation ) so previously loaded files remain in context cache, automatically compacting the session if context usage exceeds 80%. SERIALIZATION & ASYNC BUDGET: Calls are serialized (one at a time, AGY_MAX_CONCURRENCY = 1); keep follow-ups to one bounded question (<~8 minutes) or fetch in-flight runs by job_id via agy_job_result. WHEN TO USE: Multi-turn follow-up questions on an existing Session ID returned by a prior agy_delegate_research or agy_delegate_edit call. DO NOT USE FOR: Starting a brand-new research task without a prior session (use agy_delegate_research instead). RETURNS: Follow-up response, optional compaction notice, and updated session telemetry.

agy_job_resultA

Fetch the stored output or live status of an Antigravity job by job_id (or "latest"). WHEN TO USE: Retrieving the result of a long-running agy_delegate_research, agy_spawn_swarm, agy_delegate_edit, or agy_session_followup call that returned "still running, job <id>..." after reaching the soft budget (default 540s). DO NOT USE FOR: Starting a new research or edit task. RETURNS: The full completed subagent response and session telemetry if finished (done / failed / cancelled / timed_out), or "still running, job <id>, started <time>, elapsed <s>s; fetch with agy_job_result <id>" if still in flight.

agy_cancelA

Cancel a currently running or queued Antigravity job by job_id (or "active"), terminating any hung or unneeded child process tree (taskkill /T /F) and freeing the serialized agy queue immediately. WHEN TO USE: Aborting an in-flight or queued agy job shown in agy_status so subsequent calls are not blocked. DO NOT USE FOR: Read-only status checks (use agy_status or agy_job_result). RETURNS: JSON cancellation report { ok, job_id, previous_state, state, pid, elapsed_s, message } plus telemetry footer.

agy_configure_workspaceA

Update workspace environment configuration and Antigravity IDE Visual HUD settings. Auto-detects project toolchains (.venv, node_modules/.bin), registers monorepo directories (--add-dir), injects environment variables, optionally syncs .vscode/settings.json, and attaches or launches the Antigravity IDE window. WHEN TO USE: Only when configuring custom virtualenv/monorepo paths or toggling IDE Visual HUD attachment. DO NOT USE FOR: Read-only status or quota checks (use agy_status instead). RETURNS: JSON object { ide_window_attached, opened_ide_window, workspace_environment } plus telemetry footer.

agy_statusA

Inspect current system health, Gemini 5-hour/weekly quota windows, Local GPU VRAM availability (/api/ps), process queue state (active_job, waiting_jobs, recent_jobs with job_id, state, started_at, elapsed_s, tier, prompt_preview), active session context remaining, and Git worktree pre-flight status in read-only mode. WHEN TO USE: Checking whether the Local GPU worker or Gemini Argon/Flash tiers are online, inspecting in-flight/queued jobs, and checking token savings. DO NOT USE FOR: Modifying workspace settings or attaching the IDE (use agy_configure_workspace instead). RETURNS: JSON status report { agy_process_queue, local_gpu_queue, local_gpu_probe, local_gpu_telemetry, model_quotas, sessions } plus telemetry footer.

local_file_scoutA

ZERO-TRUST MEMORY TOOL: Read repository files directly from disk on the server side and use the Local GPU LLM (0x cloud quota) as a strict forensic disk-evidence extractor. Outputs verbatim signatures, imports, and logic with exact 1-based <file>:L<line> citations (<300 tokens), or "NOT_FOUND_ON_DISK: [symbol/query]" if absent (automatically escalating to Gemini 3.8 Flash if the local GPU is offline). WHEN TO USE: Always call before raw Read on unfamiliar/large files (>150 lines) or whenever verifying disk state before answering or editing. DO NOT USE FOR: Multi-directory architectural synthesis across 10+ files (use agy_delegate_research after scouting). RETURNS: Concise markdown bullet digest with <file>:L<line> citations and telemetry footer.

local_exec_and_triageA

Execute allow-listed test, build, typecheck, or lint commands (pytest, npm test, npx tsc, cargo check, go test) in a managed subprocess with Windows process-tree kill protection (taskkill /T /F) and scrub verbose output on the Local GPU (0x cloud quota). WHEN TO USE: Running any test suite, compiler check, or linter that may produce >40 lines of noisy output. DO NOT USE FOR: Chained shell commands (&&, ;, | are blocked) or file edits. RETURNS: Full output directly if <=40 lines; otherwise a Local GPU-scrubbed digest containing only exit code, failing test names, <file>:<line> locations, and isolated stack traces.

local_draft_leaf_codeA

Draft standalone leaf-node boilerplate, unit test files, DTOs, or schemas on disk using the Local GPU LLM (0x cloud quota). Reads reference_files on the server side, validates that the drafted code is >=15 chars with closed markdown fences and no truncation placeholders before writing target_file (automatically aborting disk write and escalating to agy_delegate_edit flash-high if invalid or offline). WHEN TO USE: Creating or updating a single self-contained leaf file (unit tests, schemas, types, boilerplate). DO NOT USE FOR: Complex multi-file refactoring or cross-module architectural edits (use agy_delegate_edit instead). RETURNS: Write confirmation, byte/line counts, and git diff --stat summary.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 16 tools

Disambiguation3/5

The prefix scheme separates three backends (codex_, agy_, local_), but each backend exposes near-parallel operations — codex_research vs agy_delegate_research, codex_followup vs agy_session_followup, codex_status vs agy_status, codex_cancel vs agy_cancel — so an agent must read the routing rules to pick correctly. Descriptions do a lot of work with explicit 'DO NOT USE FOR' clauses, but the overlapping research/scout/draft/edit triad (local_file_scout vs agy_delegate_research vs local_draft_leaf_code vs agy_delegate_edit) remains genuinely easy to misselect.

Naming Consistency3/5

A consistent three-prefix scheme (codex_/agy_/local_) groups tools predictably, which is a real strength. Within groups, however, conventions are mixed: verb_noun (agy_delegate_edit, agy_spawn_swarm) sits beside noun-phrase tools (agy_status, agy_job_result, codex_job_result) and odd forms like local_file_scout (noun_verb) and local_exec_and_triage.

Tool Count3/5

Sixteen tools is at the borderline of heavy, and the cost is amplified because the surface duplicates the same lifecycle (research, follow-up, status, cancel, job-result) across two agent backends plus a local tier. Each tool is justified individually, but the aggregate feels larger than the underlying domain requires.

Completeness4/5

Coverage is broad: research, editing, multi-file delegation, drafting, command execution, session follow-up, job retrieval, cancellation, status, and workspace configuration are all present, so most workflows have a path forward. Minor gaps include no generic file read/list or job-listing operation independent of the status tools, and Codex offers no edit path at all.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues