Agent Collaboration Orchestrator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SANDBOX_ROOT | No | Codex 允许访问的协同工作空间根目录。 | |
| EXECUTOR_MODEL | No | 默认模型名称，会写入任务 prompt 供执行器参考。 | |
| CODEX_EXECUTOR_ARGS | No | Codex 启动参数模板。默认通过 stdin 传入 prompt。 | |
| EXECUTOR_TIMEOUT_MS | No | Codex 子任务超时时间，默认 30 分钟。 | |
| CODEX_EXECUTOR_COMMAND | No | Codex 执行入口，例如 codex.cmd、codex.exe、node、powershell 或自定义中转脚本。 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_taskB | Submit a development task to the executor agent |
| get_task_statusC | Get the status of a task |
| get_task_logC | Get execution logs for a task |
| get_result_reportA | Get the final result report for a completed task |
| request_revisionC | Request revision for a task |
| cancel_taskB | Cancel a running or pending task |
| list_artifactsB | List files and artifacts produced by a task |
| list_tasksB | List task summaries for TRAE desktop/mobile progress views |
| get_mobile_dashboardB | Get a compact dashboard with task counts, recent tasks, and pending permission requests |
| list_permission_requestsB | List permission requests created after Codex fails due to sandbox or approval restrictions |
| resolve_permission_requestA | Approve or reject a pending permission request. Approval creates a retry task with the requested sandbox. |
| diagnose_environmentB | Check the MCP environment configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct operation: task lifecycle (submit, cancel, status, logs, artifacts, report), permissions (list, resolve), environment diagnostics, dashboard, and revision. No two tools overlap in purpose.
All tool names follow the verb_noun snake_case pattern (e.g., cancel_task, list_permission_requests). The naming is uniform and predictable across the entire set.
With 12 tools, the set is well-scoped for an agent orchestration server. Each tool serves a clear function without redundancy, and the count is appropriate for the domain complexity.
The tool surface covers the main task lifecycle (submit, cancel, status, logs, artifacts, report), permissions, environment check, and revision. Minor missing features like direct task update or retry are handled indirectly, leaving only small gaps.