Antigravity Mobile Command MCP Server

run_terminal_command

Execute shell commands in the project directory and receive stdout, stderr, and exit codes to perform builds, run tests, and troubleshoot from mobile.

Instructions

Run a terminal command in the project directory. Returns stdout, stderr, and return code. Use for builds, tests, etc.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "run_terminal_command"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Command to execute
`timeout`	No	Timeout in seconds (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. While it mentions the return values, it fails to warn that executing a terminal command can have arbitrary side effects (e.g., modifying files, running network operations, or being destructive). For a command execution tool, this is a significant safety gap.

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 exceptionally concise, front-loading the main action and output, followed by a brief usage hint. Every sentence contributes value without redundancy.

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?

For a tool with only two parameters and no output schema, the description covers the essential return values (stdout, stderr, return code) and a typical use case (builds/tests). However, it omits critical safety context and environment details, such as working directory behavior or potential side effects, which prevents a perfect score.

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?

The input schema already provides full descriptions for both parameters ('command' and 'timeout') with 100% coverage. The description adds no extra parameter-level meaning, so the baseline score of 3 is appropriate.

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 a specific action ('Run a terminal command'), the context ('in the project directory'), and the expected output ('Returns stdout, stderr, and return code'). This distinguishes it from sibling tools like read_project_file or send_telegram_message, which serve different purposes.

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 provides a clear use case ('Use for builds, tests, etc.'), which communicates when the tool is appropriate. However, it does not explicitly exclude alternatives or mention when not to use it, though the sibling tool names imply a distinct domain.

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

Deploy Server