Antigravity Mobile Command MCP Server

await_user_response

Pause the agent and prompt the user for specific input or instructions. Use this when you need user approval or additional details to proceed with a task.

Instructions

Wait for the user to respond with a message. Use when you need specific input or instructions from the user.

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": {
      "prompt": "<prompt>"
    },
    "name": "await_user_response"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Prompt to show the user
`timeout_seconds`	No	Timeout in seconds (default: 300)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It only says 'wait for the user to respond' and omits critical behavioral details such as blocking semantics, timeout behavior, and what occurs on timeout. The existence of a timeout_seconds parameter is not reflected in the description, leaving the agent uninformed.

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 two concise sentences, front-loaded with the core action, and contains no irrelevant information.

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

Completeness3/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 basic 'what' and 'when', but omits important behavior like timeout handling and return value. This makes it minimally adequate but not fully complete.

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 coverage is 100%, so both parameters are already described in the schema. The description adds no extra semantics beyond the schema's parameter descriptions, thus matching the baseline for full 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 clearly states the tool waits for a user message and is used when specific input is needed, which distinguishes it from messaging/notification tools. However, it does not explicitly differentiate from the sibling 'wait_for_new_prompt', so it stops short of full clarity.

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 ('when you need specific input or instructions from the user'), offering practical guidance. However, it lacks explicit exclusions or alternatives, so it doesn't fully meet the 'when-not-to-use' criterion.

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

Deploy Server