Antigravity MCP Bridge

Overview Schema Source Related Servers Discussions Admin

Resume Antigravity conversation

antigravity_resume

Destructive

Continue a completed session in its existing isolated copy, so you can resume coding tasks while preserving context and worktree state.

Instructions

Continue a completed session in its existing isolated copy.

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>",
      "workingDirectory": "<workingDirectory>",
      "sessionId": "<sessionId>"
    },
    "name": "antigravity_resume"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No
`role`	No
`model`	No
`prompt`	Yes
`sessionId`	Yes
`includePaths`	No
`timeoutSeconds`	No
`isolateWorktree`	No
`workingDirectory`	Yes
`acceptanceCriteria`	No

Output Schema

Name	Required	Description	Default
`task`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 1, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds only that the session continues in an existing isolated copy; it does not explain what 'continue' entails, what may be modified, or any permission or rate-limit context.

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

Conciseness2/5

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

The description is a single short sentence with no wasted words, but it is severely under-specified for a 10-parameter, destructive, open-world tool. Conciseness here reflects omission rather than efficient communication.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. However, for a complex tool with 10 parameters, no schema descriptions, and destructive behavior, the description leaves usage, parameter semantics, and operation details almost entirely unaddressed.

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

Parameters1/5

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

Schema description coverage is 0% across 10 parameters, and the description mentions none of them. It provides no meaning for prompt, sessionId, workingDirectory, mode, role, model, includePaths, timeoutSeconds, isolateWorktree, or acceptanceCriteria.

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 verb ('Continue') and resource ('a completed session'), with the scope 'in its existing isolated copy.' It is clear what the tool does, but it does not distinguish itself from siblings like antigravity_run or antigravity_sessions.

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?

The phrase 'Continue a completed session' implies usage when a session is already completed, but it gives no explicit when-to-use guidance, prerequisites, or alternatives to sibling tools such as antigravity_run.

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