Skip to main content
Glama
Sign In
antigravity-mcp-server

antigravity-mcp-server

by adeelali4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Clear the shared board

coop_reset

Remove all collaborative data—tasks, locks, notes, events, and presence—from the board to start a new project fresh. Confirmation is required to perform this destructive action.

Instructions

Clear the whole board -- tasks, locks, notes, events, presence. Destructive; requires confirm=true. Use when starting a fresh project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coop_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description discloses that the operation is destructive, requires confirm=true, and lists exactly what will be cleared, giving the agent a clear safety profile.

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?

A single, tightly worded sentence delivers the purpose, scope, safety warning, and usage context with no redundant words.

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 destructive one-parameter tool with no output schema, the description covers what is cleared, when to use it, and the confirmation requirement; it could explicitly mention irreversibility but the 'Destructive' label suffices.

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

Parameters5/5

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

The schema lists no descriptions, but the description explicitly states that confirm=true is required, clarifying the sole parameter's purpose and correcting the schema's optionality.

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?

Clearly states it clears the whole board and enumerates the elements (tasks, locks, notes, events, presence), distinguishing it from sibling tools like board_update or board_list.

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?

Provides a specific use case ('Use when starting a fresh project') and warns that it is destructive, but does not explicitly name alternative tools or exclusion criteria.

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