Antigravity Mobile Command MCP Server

set_project_context

Set the project directory for IDE operations, making all subsequent file operations relative to that path.

Instructions

Set the current project path for IDE operations. All file operations will be relative to this path.

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": {
      "project_path": "<project_path>"
    },
    "name": "set_project_context"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	Absolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/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 discloses an important behavioral trait—file operations become relative to this path—but lacks details about persistence, validation, or what happens if the path is invalid. This is adequate but not comprehensive.

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?

Two sentences, front-loaded with the core action, and zero wasted words. It efficiently communicates both purpose and effect.

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 simple setter tool with one parameter and no output schema, the description is fairly complete. It explains what the tool does and its effect on other operations. Missing details like persistence or how to query the current context are minor given the tool's simplicity and the presence of get_project_context among siblings.

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 the schema already documents the parameter as 'Absolute path to the project directory.' The description adds the behavioral context that file operations will be relative, but does not add further parameter-specific syntax or format details beyond the schema.

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 the tool's function: 'Set the current project path for IDE operations.' It uses a specific verb ('set') and resource ('project path'), and distinguishes from sibling tools like get_project_context by indicating it sets rather than retrieves context.

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?

The description implies when to use the tool by stating 'All file operations will be relative to this path,' which signals it should be called before file operations. It does not explicitly name alternatives like get_project_context, but the context is clear enough for an agent to infer usage.

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

Deploy Server