Skip to main content
Glama
Sign In
Codex Antigravity Subagent MCP

Codex Antigravity Subagent MCP

by zamatewi-cell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

检查 Antigravity 子代理状态

antigravity_status
Read-only

Verify the AGY CLI version, list available models, and confirm the default gemini-3.8-flash-high model is present to avoid runtime failures before starting tasks.

Instructions

检查 AGY CLI 版本、可用模型，以及默认模型 gemini-3.8-flash-high 是否存在。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "antigravity_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world safety profile. The description adds useful behavioral scope by stating exactly what is inspected: CLI version, available models, and the presence of the default model. No contradiction with annotations.

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 a single concise sentence with the action and checked resources front-loaded. It contains no filler, tautology, or unnecessary background.

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?

For a zero-parameter, read-only status tool with supporting annotations, the description names all relevant checks and is sufficient for an agent to select and invoke it correctly. The lack of an output schema is not a significant gap given the low invocation complexity.

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

Parameters4/5

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

The tool has zero parameters and the schema contains an empty properties object, so there is no parameter detail to document. The description appropriately focuses on what the status check reports rather than inputs.

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 uses a specific verb ('检查') and concrete resources: AGY CLI version, available models, and whether the default model gemini-3.8-flash-high exists. This clearly distinguishes it from sibling task-management tools like delegate_to_gemini or cancel_gemini_task.

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

Usage Guidelines3/5

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

Usage is implied from the tool's nature as a status/health-check command, but the description does not explicitly say when to use it versus alternatives or provide any exclusions. No comparable status-checking sibling is named, so the guidance is implicit rather than explicit.

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