Skip to main content
Glama
JamesZor

Antigravity MCP Server

by JamesZor

start_background_job

Run a prompt as a background job on Antigravity with configurable model tier, workspaces, auto-approval, sandbox, session continuation, and timeout. Returns a job ID for status checks.

Instructions

Start a long-running Antigravity (agy/Gemini) task in the background.
Returns a job_id that can be used to check status.

Args:
    prompt: The task prompt to send to Antigravity.
    tier: Model tier (flash, flash-med, flash-lo, pro, pro-lo, sonnet, opus, gpt-oss). Default is flash.
    dirs: Workspaces to attach so agy reads real files.
    yolo: Auto-approve all tool permissions (DANGEROUS). Required for web search.
    sandbox: Run agent with terminal sandbox restrictions.
    continue_session: Resume the most recent agy conversation (stateful).
    conversation_id: Resume a specific agy conversation by ID (stateful).
    timeout: Print-mode timeout, e.g., '10m'. Default is '5m'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dirsNo
tierNoflash
yoloNo
promptYes
sandboxNo
timeoutNo5m
conversation_idNo
continue_sessionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses dangerous behavior (yolo) and sandbox restrictions, but could mention failure handling or concurrency limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with purpose and return value, then clear parameter list. No superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 8 parameters and existence of output schema, the description covers all aspects needed for correct invocation, including parameter details and return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description explains each of the 8 parameters in detail, including values and warnings, fully compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it starts a long-running Antigravity task in the background and returns a job_id. It specifies the association with 'agy/Gemini' and differentiates from sibling tools like 'check_job_status'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the tool is for background tasks, implying when to use it. It doesn't explicitly list when not to use, but the context of sibling tools provides clarity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JamesZor/antigravity'

If you have feedback or need assistance with the MCP directory API, please join our Discord server