Skip to main content
Glama

Stop an Antigravity conversation process

agy_stop

Stop a conversation's agent process to free memory while keeping its state on disk for later resumption.

Instructions

Close the agent process for a conversation to free memory. The conversation's memory stays on disk and can be resumed later with agy_resume. Defaults to the current default conversation.

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

Input Schema

NameRequiredDescriptionDefault
conversation_idNoConversation id to stop (default: the current default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does well on the most important trait — the conversation's memory persists on disk and can be resumed — but says nothing about in-flight requests, idempotency if the process is already stopped, or failure modes.

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?

Three short sentences, front-loaded with purpose, then the persistence guarantee, then the default. No filler or repetition.

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 zero-required-parameter termination tool with no output schema, the description covers purpose, data safety, recovery path, and the default behavior. Minor gap around what happens to any work in progress.

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% and the single conversation_id parameter is already documented with its default. The description's closing sentence about defaulting to the current conversation merely restates the schema, adding no new semantics.

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?

States a specific verb and resource ("Close the agent process for a conversation") plus the reason it exists ("to free memory"), which is enough for an agent to distinguish it from agy_resume and the ask/conversations siblings.

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?

Implies the when-to-use case (freeing memory) and explicitly routes the agent to agy_resume for the opposite operation, but gives no explicit exclusions such as a warning against stopping a conversation mid-answer.

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