Skip to main content
Glama
Sign In
antigravity-mcp

antigravity-mcp

by NohchiyBors
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_chat

Engage in interactive chat with Antigravity, preserving context across sessions and resuming past conversations by ID.

Instructions

Engage in an interactive chat session with Antigravity, preserving or resuming conversation threads.

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": "agy_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
modelNo
promptYesMessage to send to the conversation
continueRecentNoContinue the most recent active conversation
conversationIdNoResume a past conversation by ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 for behavioral transparency. It does disclose a key behavioral trait: the tool is stateful, as it can preserve or resume conversation threads. However, it does not explain side effects such as creating new conversations, returning responses, or any authentication/rate-limit implications, leaving significant gaps.

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 that immediately conveys the tool's purpose and key capability (preserving/resuming threads). There is no redundant information or filler, making it highly efficient.

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?

Despite having 5 parameters, no output schema, and no annotations, the description remains very sparse. It fails to explain how to configure the chat (e.g., choosing agent or model), what the response format looks like, or the behavior when no conversation context is provided. This leaves substantial gaps for an agent attempting to invoke the tool correctly.

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 schema description coverage is 60% (3 of 5 parameters have descriptions), so the baseline is 3. The description adds context by referencing conversation thread management, which aligns with the continueRecent and conversationId parameters, but it does not elaborate on the meaning of agent or model parameters, nor does it clarify the relationship between the state-related parameters.

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 identifies the tool as an interactive chat session with Antigravity, with the specific function of preserving or resuming conversation threads. It distinguishes itself from sibling tools by focusing on conversational interaction, although it does not explicitly name any alternative.

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 description implies usage for multi-turn conversational interactions by mentioning preserving or resuming conversation threads, but it does not provide explicit guidance on when to use this tool versus alternatives such as agy_autonomous_agent or agy_sandbox_agent. No exclusions or alternative conditions are stated.

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