Skip to main content
Glama
lhdhtrc

antigravity

by lhdhtrc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

antigravity_submit

Launch a long-running Antigravity analysis in the background and get an immediate job ID, so you can retrieve results later without blocking your session.

Instructions

在后台启动一轮 Antigravity 作业并立刻返回 job id。长作业（深度分析、长文档）用它避免阻塞；之后用 antigravity_job 取结果。参数与 antigravity_ask 相同。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoAntigravity 会话的工作目录（即它的 workspace）。
diffNoAttach the working tree diff (captured locally with git) as context; handy for 'review my changes' without the agent having to run git itself.
modeNoAntigravity 执行模式；省略则用 CLI 默认。
agentNo可选的 Antigravity agent 名称。
filesNoPaths the Antigravity agent should read itself before answering, instead of pasting file contents into the prompt.
modelNoAntigravity model id (see antigravity_models), or 'auto' to pick one whose quota group still has room. Default: gemini-3.8-flash-high.
effortNo本会话的思考强度。
no_webNoTell the agent not to browse or use browser tools. Use it for analysis tasks: browsing costs many steps and the CLI's browser driver is often unavailable.
promptYes发送给 Antigravity CLI 的提示词（非交互 print 模式）。
handoffNoCompact the current conversation into a handoff digest, start a NEW conversation and answer there with that digest as background. Use when the conversation has grown long.
sandboxNo以终端受限方式运行会话（默认 true）。
sessionNoNamed Antigravity conversation to keep continuity across calls. Calls with the same session name resume the same conversation; use new_session to restart it.default
diff_baseNo配合 diff 指定对比的 git ref（默认 HEAD）。
extra_argsNo追加的 agy 原始参数，原样拼接。
json_schemaNoOptional JSON schema (inline string or path) passed to the CLI with --json-schema, so the Antigravity answer is structured. Implies a per-schema session process.
new_sessionNo为该会话重开一个会话，而不是续接已记录的那个。
timeout_secNo等待 Antigravity CLI 的秒数上限。
conversationNo指定要续接的会话 id（覆盖本会话记录的那个）。
output_formatNoCLI print 模式的输出格式，原样返回。text
continue_sessionNo续接最近一次 Antigravity 会话。
skip_permissionsNoAuto-approve Antigravity tool permissions (default true). Headless runs cannot prompt for approval, so without this the agent cannot even read a file; the terminal sandbox stays on unless you disable it.
disable_slash_commandsNo不展开提示词里的斜杠命令与技能（默认 true）。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It clearly discloses the core behavioral trait: the tool returns a job id immediately and runs in the background, and results come later via antigravity_job. It could add more (e.g., failure behavior, quota/session implications), but the essential async/non-blocking semantics are well covered without contradicting anything.

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?

Three compact sentences with zero waste: purpose and return value first, then usage scenario, then follow-up tool. Every sentence earns its place and the most important information (background + job id) is front-loaded.

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

Completeness4/5

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

Despite 22 parameters and no output schema, the description covers the essential flow: what it returns (job id), when to use it, and how to retrieve results afterward. It doesn't describe failure modes or job lifecycle details, but the critical async workflow is complete enough for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100% — all 22 parameters have descriptive text in the schema itself, so the schema does the heavy lifting. The description adds a cross-reference (参数与 antigravity_ask 相同) rather than per-parameter detail, which is appropriate given the full schema coverage. Baseline 3 is correct.

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 states a specific action (启动一轮 Antigravity 作业, start an Antigravity job) in the background and its immediate return value (job id). It clearly differentiates from siblings: it's the async counterpart to antigravity_ask and precedes antigravity_job. The purpose is unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use it (长作业/深度分析/长文档 to avoid blocking) and the follow-up flow (之后用 antigravity_job 取结果), which routes the agent between the async submit tool and the result-fetching sibling. This is strong when-to-use guidance with a named alternative.

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

Deploy Server

Other Tools