Skip to main content
Glama
Secret-art-stack

spillway-mcp

by Secret-art-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_delegate_edit

Delegates coordinated edits across multiple existing files to Antigravity, returning an edit summary and optional IDE diff confirmation for review.

Instructions

Delegate complex multi-file code modifications or cross-module refactoring to Antigravity (agy) in --mode=accept-edits. WHEN TO USE: Coordinated edits across multiple existing files requiring Gemini Argon/Flash reasoning. DO NOT USE FOR: Generating a single standalone boilerplate, DTO, schema, or unit test file (use local_draft_leaf_code instead at 0x quota), read-only analysis (use agy_delegate_research), or running test suites (use local_exec_and_triage). RETURNS: Edit summary, optional IDE visual diff confirmation, and telemetry footer.

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional working directory path.
tierNoGemini model tier to execute the edit (defaults to argon-medium).argon-medium
promptYesClear multi-file editing instructions and target file scope for Antigravity.
allow_shellNoIf false (default), runs with --mode=accept-edits (file edits only). If true, requests --dangerously-skip-permissions (refused unless AGY_ALLOW_SKIP_PERMISSIONS=1 is configured).
target_filesNoOptional list of target file paths being edited so the Visual HUD can snapshot and open inline diffs (--diff) in Antigravity IDE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / allow_shell / default
      Added value: +false
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional working directory."New value: +"Optional working directory path."
    • changedInput schema / properties / prompt / description
      Previous value: -"Clear editing instructions and scope for Antigravity."New value: +"Clear multi-file editing instructions and target file scope for Antigravity."
    • addedInput schema / properties / prompt / minLength
      Added value: +1
    • addedInput schema / properties / tier / default
      Added value: +"argon-medium"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent. The description adds real value beyond that: the default --mode=accept-edits file-edit-only behavior, the escalation path via allow_shell gated behind AGY_ALLOW_SKIP_PERMISSIONS=1, and what is returned (edit summary, IDE diff confirmation, telemetry footer). It doesn't cover failure behavior or whether edits are revertible, keeping it below a 5.

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 labeled blocks (action, WHEN TO USE, DO NOT USE FOR, RETURNS) with the core action front-loaded. Dense but every sentence carries routing or behavioral information; no filler.

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?

No output schema exists, and the description compensates by listing return contents. For a mutation tool with five params this is largely sufficient, though it omits error/failure handling and any note on whether accepted edits are recoverable.

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 property descriptions already explain cwd, tier defaults, prompt scope, allow_shell gating, and target_files' HUD/diff purpose. The description adds little parameter-level detail beyond echoing the accept-edits mode. Baseline 3 is appropriate when the schema carries the 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?

States a specific verb+resource (delegate multi-file code modifications / cross-module refactoring) to a named executor in a named mode. It explicitly contrasts itself with `local_draft_leaf_code`, `agy_delegate_research`, and `local_exec_and_triage`, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has an explicit WHEN TO USE condition (coordinated edits across multiple existing files needing Gemini Argon/Flash reasoning) and a DO NOT USE FOR block naming three alternatives with their own scoping conditions. Exclusions and alternatives are both spelled out.

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