Skip to main content
Glama
josephjerryrhule

agy-mcp

by josephjerryrhule
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

agy_continue

Resume an ongoing coding conversation to apply follow-up adjustments, fix tests, or iterate on tasks, with live streaming and token savings tracking.

Instructions

Continues an existing Antigravity conversation for follow-up adjustments, revisions, test fixing, or iterative tasks with real-time streaming and token savings tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asyncNoRun task asynchronously in background. RECOMMENDED in Claude Desktop for any real coding tasks (>45s) to avoid 60s MCP client timeouts. Check status with agy_check_task.
effortNoReasoning effort.high
instructionsYesFollow-up instructions, corrections, or next steps for the agent.
workspace_dirNoTarget workspace directory path (MANDATORY in Claude Desktop to point to the project repo). Defaults to current working directory.
conversation_idYesThe conversation ID returned from a prior agy_execute or agy_continue call.
timeout_secondsNoMax execution time in seconds.
include_git_diffNoInclude git status and diff summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • addedInput schema / properties / async
      Added value: +{
+  "default": false,
+  "description": "Run task asynchronously in background. RECOMMENDED in Claude Desktop for any real coding tasks (>45s) to avoid 60s MCP client timeouts. Check status with agy_check_task.",
+  "type": "boolean"
+}
    • changedInput schema / properties / workspace_dir / description
      Previous value: -"Target workspace directory path (absolute path recommended, especially in Claude Desktop)."New value: +"Target workspace directory path (MANDATORY in Claude Desktop to point to the project repo). Defaults to current working directory."
  2. Changed1 schema field changedv1.2.1
    • changedInput schema / properties / workspace_dir / description
      Previous value: -"Target workspace directory path."New value: +"Target workspace directory path (absolute path recommended, especially in Claude Desktop)."
  3. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully mentions real-time streaming and token savings tracking, but it does not describe side effects, background execution behavior, or failure modes. Some behavior is recoverable from schema fields like async and workspace_dir, but the description could be more explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One focused sentence that starts with the action and then enumerates relevant use cases and key behavioral features. It is reasonably concise with no filler, though the comma-heavy list makes it slightly less scannable than a two-sentence version.

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

Completeness3/5

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

The description helps the agent know the high-level purpose and useful behavioral details, and the schema documents all parameters. It leaves the exact return/output shape and the relative comparison with agy_execute implicit, so some contextual decisions are still on the agent.

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 input schema has 100% documented parameters, so the schema does the primary lifting. The description adds context about streaming and token tracking but does not add meaning to individual parameters. Baseline score of 3 is appropriate given the full schema coverage.

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 uses a clear verb-resource pairing: 'continues an existing Antigravity conversation' and backs it with concrete use cases such as follow-up adjustments, revisions, test fixing, and iterative tasks. The word 'existing' differentiates it from agy_execute and similar initial-execution siblings.

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 gives an implied usage scenario: use it when a conversation already exists and needs continuation. It names the use cases but never explicitly contrasts it with agy_execute or says 'use agy_execute for a new conversation', so routing between siblings is left to the agent's inference.

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