Skip to main content
Glama
lhdhtrc

antigravity

by lhdhtrc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

antigravity_ask

Send a prompt to the local Antigravity CLI and receive the answer, resuming the same session and using your own subscription quota instead of the provider's.

Instructions

通过本机 Antigravity CLI（agy）跑一轮非交互提问并返回回答；默认续接同一会话。用的是 agy 已登录的 Google 账号额度（Antigravity / Gemini），不占用当前供应商的额度。

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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that it uses agy's Google account quota and continues the same session by default, but it omits potential side effects such as file modifications, command execution, or permission handling. For a tool that runs an AI agent, this is a significant gap.

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

Conciseness4/5

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

The description is a single sentence, very concise and front-loaded with the core action and quota note. It avoids verbosity, though given the tool's complexity it may be too brief. Still, it is efficient and well-structured.

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

Completeness2/5

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

With 22 parameters and no output schema, the description is inadequate. It does not describe the return format, error behavior, or how session continuity works in practice. The quota and session notes are helpful but insufficient for an agent to use this tool correctly without diving into the schema.

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%, so all 22 parameters have descriptions. The tool description adds no extra parameter meaning beyond what the schema already provides; the mention of session continuation aligns with the session parameter but is already documented there. Baseline 3 is appropriate given the high schema coverage.

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

Purpose4/5

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

The description states a specific action: run a non-interactive question via the local Antigravity CLI and return the answer, and notes default session continuation and quota usage. However, it does not differentiate from sibling tools like antigravity_submit or antigravity_job, so an agent cannot tell them apart without inspecting their schemas.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. It does not mention conditions, exclusions, or contexts where another sibling would be more appropriate. The only hint is the quota note, but that is about resource usage, not selection criteria.

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