Skip to main content
Glama
MauricioPerera

subway-mcp-server

Delegate task to Claude Code CLI

delegate_to_claude
Destructive

Run a task non-interactively with Claude Code, capturing its final response. Delegates work to an autonomous sub-agent for execution.

Instructions

Runs Claude Code non-interactively (claude -p --output-format json) to execute a task and returns its final message.

Args:

  • prompt (string, required): task instructions for Claude

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

  • model (string, optional): model override (e.g. "claude-opus-4-8")

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

  • auto_approve (boolean, optional, default false): bypass Claude'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? }.

Error Handling:

  • success=false with a non-zero exit_code and stderr populated means the CLI reported an error (e.g. auth, invalid model)

  • 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?

Adds substantial behavioral details beyond annotations: describes process killing on timeout, structured return value format, and error handling (success, exit_code, timed_out, stderr). Annotations indicate destructiveHint=true, and the description warns of side effects via auto_approve. No contradictions.

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?

Well-structured with sections for args, return format, and error handling. Every sentence is informative and earns its place. No redundancy.

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 full schema coverage, output schema, and annotations, the description is highly complete. Covers purpose, usage caveats, return values, error states, and parameter details comprehensively.

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% with good descriptions for each parameter. The description does not add significant new meaning beyond summarizing the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it runs Claude Code CLI non-interactively to execute a task and returns the final message. Includes the exact CLI invocation format. Names sibling tools but does not explicitly contrast them, so slightly below top tier.

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?

Explains the non-interactive context and warns that auto_approve is needed for tool-using tasks (otherwise they fail). Provides implicit when-to-use guidance for unattended execution. Lacks explicit when-not-to-use or comparison with alternatives.

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