Skip to main content
Glama
MauricioPerera

subway-mcp-server

Delegate task to Antigravity (agy) CLI

delegate_to_agy
Destructive

Execute tasks by delegating them to the Antigravity CLI sub-agent, with optional auto-approval of tool permissions to prevent interactive prompt failures.

Instructions

Runs the Antigravity CLI non-interactively (agy -p) to execute a task and returns its response.

Args:

  • prompt (string, required): task instructions for the agy agent

  • cwd (string, optional): absolute working directory for the task

  • model (string, optional): model override

  • timeout_seconds (number, optional, default 600): kill the process after this many seconds

  • auto_approve (boolean, optional, default false): bypass agy's tool-permission prompts (--dangerously-skip-permissions). Without this, tasks that need to use tools will fail immediately since there is no terminal to approve from.

Returns structured JSON: { success, final_message, exit_code, timed_out, stderr? }. Note: agy has no JSON output mode, so final_message is the raw trimmed stdout.

Error Handling:

  • success=false with a non-zero exit_code and stderr populated means the CLI reported an error

  • timed_out=true means the task exceeded timeout_seconds and was killed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoAbsolute path to the working directory the sub-agent should operate in. Defaults to this MCP server's own working directory if omitted.
modelNoModel override for this run (e.g. 'gpt-5.6-luna', 'claude-opus-4-8'). Omit to use the CLI's own configured default.
promptYesTask instructions for the sub-agent to execute, exactly as it should receive them.
auto_approveNoBypass the sub-agent's interactive tool-permission prompts (shell commands, file edits, etc). This call has no terminal attached, so without auto_approve most non-trivial tasks will fail immediately the first time the sub-agent needs to use a tool. Set true when you trust the task to run unattended.
timeout_secondsNoHow long to wait for the sub-agent to finish, in seconds (10-1800, default 600). The process is killed if it runs longer.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stderrNoCaptured stderr, included only when the run was not successful.
successYesTrue if the sub-agent process exited with code 0 and did not time out.
exit_codeYesProcess exit code, or null if the process could not be spawned.
timed_outYesTrue if the process was killed after exceeding timeout_seconds.
final_messageYesThe sub-agent's final response text.
Behavior5/5

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

The description discloses output format, error handling, timeout behavior, and the necessity of auto_approve for tool-using tasks. This goes well beyond the annotations, which are already present.

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 well-structured with a summary line, parameter listing, return format, and error handling. It is concise and front-loaded with the essential purpose.

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?

Given the tool's complexity (5 parameters, output schema, annotations), the description covers return values, error cases, and operational nuances, making it fully complete.

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 coverage is 100%, but the description adds valuable context for parameters like auto_approve (explaining failure without it) and timeout (kill behavior), exceeding the baseline of 3.

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 clearly states it runs the Antigravity CLI non-interactively to execute a task, using a specific verb and resource. The title and description distinguish it from sibling tools by naming the specific CLI.

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 description implies when to use (delegating to Antigravity CLI) and highlights the need for auto_approve, but does not explicitly compare with siblings or state when not to use it.

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/MauricioPerera/subway-mcp-server'

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