Skip to main content
Glama
Secret-art-stack

spillway-mcp

by Secret-art-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_delegate_research

Read-onlyIdempotent

Delegate complex multi-file, read-only codebase research, architectural analysis, root-cause tracing, or security verification to Google Antigravity CLI and receive cited Markdown reports.

Instructions

Delegate deep read-only codebase research, cross-module architectural analysis, bug root-cause tracing, or security verification to Google Antigravity CLI (agy) using verified Gemini 3.8 Flash or Gemini 4 Argon models in --mode=plan. WHEN TO USE: Complex multi-file reasoning or architectural audits across 5–30+ files after initial scouting. DO NOT USE FOR: Simple signature, import, or line-number extraction on known files (use local_file_scout instead at 0x quota) or parallel disjoint directory scans (use agy_spawn_swarm instead). RETURNS: Markdown analysis with : citations and telemetry footer.

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional working directory path (defaults to workspace root).
tierYesGemini routing tier: flash-low/flash-medium (1x triage), flash-high (2x module summary), argon-low/argon-medium (4x cross-module reasoning), argon-high (6x apex architecture/security).flash-medium
promptYesDetailed research or analysis prompt for Antigravity. Name the specific files to inspect.
files_to_followNoOptional list of <file>:<line> targets (e.g. ["src/index.ts:42"]) to jump to in the Antigravity IDE HUD.
html_artifact_nameNoOptional filename (e.g. "arch-overview.html") to instruct agy to write a self-contained visual HTML report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional working directory (defaults to workspace root)."New value: +"Optional working directory path (defaults to workspace root)."
    • changedInput schema / properties / files_to_follow / description
      Previous value: -"Optional list of file:line targets to jump to in the Antigravity IDE HUD."New value: +"Optional list of <file>:<line> targets (e.g. [\"src/index.ts:42\"]) to jump to in the Antigravity IDE HUD."
    • changedInput schema / properties / html_artifact_name / description
      Previous value: -"Optional filename (e.g. \"arch-overview.html\") to instruct agy to write a visual diagram/report into %USERPROFILE%\\.gemini\\antigravity\\html_artifacts\\."New value: +"Optional filename (e.g. \"arch-overview.html\") to instruct agy to write a self-contained visual HTML report."
    • changedInput schema / properties / prompt / description
      Previous value: -"Detailed research or analysis prompt for Antigravity."New value: +"Detailed research or analysis prompt for Antigravity. Name the specific files to inspect."
    • addedInput schema / properties / prompt / minLength
      Added value: +1
    • addedInput schema / properties / tier / default
      Added value: +"flash-medium"
    • changedInput schema / properties / tier / description
      Previous value: -"Gemini routing tier: flash-low/flash-medium (Tier 1 triage), flash-high (Tier 2 heavy summary), argon-low/argon-medium (Tier 3 deep reasoning), argon-high (Tier 4 apex architecture/security)."New value: +"Gemini routing tier: flash-low/flash-medium (1x triage), flash-high (2x module summary), argon-low/argon-medium (4x cross-module reasoning), argon-high (6x apex architecture/security)."
  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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety burden is largely covered. The description supplements this with the return shape (Markdown with <file>:<line> citations and a telemetry footer) and a quota signal ('0x quota' for the local alternative, implying agy calls consume quota). It stops short of stating cost/latency expectations per tier or any auth prerequisites.

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?

Dense but fully front-loaded: purpose first, then WHEN TO USE, DO NOT USE FOR, and RETURNS as labeled clauses. Every clause carries routing or behavioral information; nothing is 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 describing the return format (Markdown analysis with file:line citations plus telemetry footer). Combined with explicit routing guidance and full schema coverage, an agent has what it needs to call it correctly; only cost/quota-consumption per tier and expected latency are left unstated.

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%, so all five parameters are already documented in-schema, and the description adds essentially nothing about individual parameters beyond corroborating flash/argon model naming for the `tier` enum. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific verb (delegate) and a concrete resource (deep read-only codebase research, architectural analysis, root-cause tracing, security verification) plus the target executor (Google Antigravity CLI in --mode=plan). The scope ('complex multi-file reasoning... 5–30+ files') distinguishes it cleanly from the shallow-scouting and swarm siblings.

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?

Explicit WHEN TO USE ('complex multi-file reasoning or architectural audits across 5–30+ files after initial scouting') and explicit DO NOT USE FOR with named alternatives: `local_file_scout` for signature/import/line-number extraction and `agy_spawn_swarm` for parallel disjoint directory scans. Both exclusions name a concrete sibling from the available set.

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