Skip to main content
Glama
Secret-art-stack

spillway-mcp

by Secret-art-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_configure_workspace

Idempotent

Configures workspace environment and Antigravity IDE HUD settings: auto-detects toolchains, registers monorepo dirs, injects env vars, and syncs .vscode settings for subagent runs.

Instructions

Update workspace environment configuration and Antigravity IDE Visual HUD settings. Auto-detects project toolchains (.venv, node_modules/.bin), registers monorepo directories (--add-dir), injects environment variables, optionally syncs .vscode/settings.json, and attaches or launches the Antigravity IDE window. WHEN TO USE: Only when configuring custom virtualenv/monorepo paths or toggling IDE Visual HUD attachment. DO NOT USE FOR: Read-only status or quota checks (use agy_status instead). RETURNS: JSON object { ide_window_attached, opened_ide_window, workspace_environment } plus telemetry footer.

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional workspace root directory path.
add_dirsNoAdditional directories to include in the agy workspace via --add-dir (e.g. ["../shared-types"]).
attach_ideNoSet true if this workspace is already open in Antigravity IDE to enable follow_files / visual_review_gate; set false to prevent --reuse-window from touching another project window.
follow_filesNoEnable or disable active editor file:line jumping.
env_overridesNoKey-value string environment variables (e.g. {"NODE_ENV": "test"}) injected into every subagent run.
open_ide_windowNoIf true, launches Antigravity IDE pointed specifically at this workspace folder and marks ide_window_attached=true.
vscode_settingsNoOptional key-value settings to merge non-destructively into .vscode/settings.json for Antigravity IDE.
extra_path_entriesNoAdditional PATH directories (e.g. custom toolchain or virtualenv bin folders) injected into every subagent execution.
python_interpreterNoExplicit Python interpreter path to sync into .vscode/settings.json.
visual_review_gateNoEnable or disable inline --diff tabs on delegated edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / attach_ide / default
      Added value: +false
    • changedInput schema / properties / attach_ide / description
      Previous value: -"Set true if the user already has this workspace open in Antigravity IDE and wants follow_files / visual_review_gate active; set false to prevent --reuse-window from touching another project window."New value: +"Set true if this workspace is already open in Antigravity IDE to enable follow_files / visual_review_gate; set false to prevent --reuse-window from touching another project window."
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional workspace root directory."New value: +"Optional workspace root directory path."
    • addedInput schema / properties / env_overrides / additionalProperties
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / env_overrides / description
      Previous value: -"Key-value environment variables injected into every agy subagent run."New value: +"Key-value string environment variables (e.g. {\"NODE_ENV\": \"test\"}) injected into every subagent run."
    • changedInput schema / properties / extra_path_entries / description
      Previous value: -"Additional PATH directories (e.g. custom toolchain or virtualenv bin folders) injected into every agy subagent execution."New value: +"Additional PATH directories (e.g. custom toolchain or virtualenv bin folders) injected into every subagent execution."
    • addedInput schema / properties / follow_files / default
      Added value: +true
    • addedInput schema / properties / open_ide_window / default
      Added value: +false
    • addedInput schema / properties / visual_review_gate / default
      Added value: +true
    • addedInput schema / properties / vscode_settings / additionalProperties
      Added value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean"
+  ]
+}
    • addedInput schema / required
      Added value: +[]
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real side-effect context beyond that: it mutates .vscode/settings.json, can launch or attach an IDE window, and injects env vars into every subagent run. It stops short of saying whether launching the IDE window is reversible or what happens on conflicting settings, but that gap is minor given annotation coverage.

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?

Front-loaded with the verb and resource, then structured into WHEN TO USE, DO NOT USE FOR, and RETURNS blocks. The opening sentence is long but every clause maps to a real capability; nothing is filler, though it could be split for easier scanning.

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?

For a 10-parameter, all-optional tool with nested objects and no output schema, the description covers what the tool does, when to call it, what not to call it for, and explicitly inflates the return shape ({ ide_window_attached, opened_ide_window, workspace_environment }). Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still earns extra credit by explaining the mechanics behind the parameters: auto-detected toolchains, the --add-dir mechanism, and that env/extra_path values propagate to every subagent execution — semantics the schema does not state.

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 opening sentence names a specific verb (update) and a concrete resource (workspace environment configuration + IDE Visual HUD settings), then enumerates the actual operations: toolchain auto-detection, --add-dir registration, env var injection, .vscode/settings.json sync, and IDE window attach/launch. This is clearly distinguishable from mutation siblings like agy_spawn_swarm or agy_delegate_edit, which operate on agents rather than workspace config.

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 (custom virtualenv/monorepo paths, toggling HUD attachment) and DO NOT USE FOR (read-only status/quota checks, with `agy_status` named as the alternative). The routing condition is unambiguous, so an agent can pick between this and agy_status without inspecting either schema.

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