Skip to main content
Glama
SinanTufekci

agent-intern

by SinanTufekci
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Continue Antigravity conversation

antigravity_continue

Resume the exact Antigravity conversation for a workspace with a follow-up prompt, preserving the original thread even after other agy sessions run elsewhere.

Instructions

Continue the Antigravity conversation rooted at this workspace.

Resumes the exact conversation id recorded for workspace (via agy's --conversation flag), not agy's global "most recent", so it stays correct even if agy was used elsewhere in between. On agy 1.1.8+ that id is the one agy itself reported for this bridge's last run in the workspace, so a follow-up resumes THIS thread even if you have since started a separate conversation in the same folder from Antigravity's own interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNoIf true, run this turn in agy's PLAN mode (1.1.12+) — it investigates and writes an implementation plan instead of editing files or running commands, while reads still work. Per-invocation like `model`, so a follow-up can plan even if the original ask was unrestricted. See antigravity_ask's `plan` for what it does and does not guarantee. Default false.
modelNoOptional model slug for this turn (agy's --model), e.g. "claude-sonnet-4-6". agy's model is per-invocation, not baked into the conversation, so a follow-up can run on a different model than the original ask — omit to use agy's settings.json default. Validated against `agy models`; an unknown slug is rejected (agy would silently ignore it).
watchNoIf true, open a live "watch" view in your browser that streams agy's steps as it works (same return value, best-effort). Default false.
promptYesFollow-up message.
schemaNoOptional JSON Schema for this turn — returns the validated object as JSON text instead of prose. Per-invocation like `model` and `plan`. See antigravity_ask's `schema`. Needs agy 1.1.8+.
timeout_sNoMax seconds to wait for agy to complete. Default 180.
workspaceNoWorking directory used by the prior conversation. Defaults to cwd.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations already signal mutating, open-world, non-idempotent behavior. The description adds useful behavioral context: the exact conversation id routing, version-dependent behavior on agy 1.1.8+, and the guarantee that it resumes THIS thread even if a separate conversation was started in the same folder. No contradiction with annotations.

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 two short, purposeful paragraphs. The first states the core purpose; the second adds a necessary edge-case clarification about global 'most recent' versus the exact conversation thread. Every sentence earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 100% schema coverage, rich per-parameter descriptions, an output schema, and safety/open-world annotations, the description only needs to disambiguate conversation routing behavior, which it does thoroughly. It is complete enough for an agent to select and 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?

Schema description coverage is 100%, and each parameter already has a detailed description, so the tool description does not need to explain parameters. It adds some conceptual context about how workspace maps to the recorded conversation id, but the schema carries the semantic load.

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 states exactly what the tool does: 'Continue the Antigravity conversation rooted at this workspace' and explains it resumes the exact conversation id recorded for the workspace. This clearly distinguishes it from starting a new ask and from other sibling tools.

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 first sentence frames when to use the tool, and the second paragraph clarifies that it uses the workspace-recorded conversation id rather than agy's global 'most recent', preventing common misuse. It does not explicitly name antigravity_ask as the alternative for starting new conversations, so it stops short of full when/not guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SinanTufekci/agent-intern'

If you have feedback or need assistance with the MCP directory API, please join our Discord server