Skip to main content
Glama
x51xxx
by x51xxx

batch

Delegate multiple atomic tasks to GitHub Copilot CLI for batch processing, repetitive operations, mass refactoring, and automated code transformations.

Instructions

Delegate multiple atomic tasks to GitHub Copilot CLI for batch processing. Ideal for repetitive operations, mass refactoring, and automated code transformations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoAI model to use: 'gpt-5', 'claude-sonnet-4', 'claude-sonnet-4.5', or 'claude-haiku-4.5' (0.33x cost). Defaults to COPILOT_MODEL env var
tasksYesArray of atomic tasks to delegate to GitHub Copilot
addDirNoAdd directories to allowed list for file access
resumeNoResume from a previous session (optionally specify session ID)
timeoutNoMaximum execution time per task in milliseconds
continueNoResume the most recent session
denyToolNoDeny specific tools
logLevelNoSet the log level
parallelNoExecute tasks in parallel (experimental)
allowToolNoAllow specific tools. Supports glob patterns (e.g., 'shell(npm run test:*)')
workingDirNoWorking directory for command execution. Falls back to COPILOT_MCP_CWD env var or process.cwd()
stopOnErrorNoStop execution if any task fails
allowAllPathsNoAutomatically approve access to all file paths (use with caution)
allowAllToolsNoAllow all tools to run automatically
additionalMcpConfigNoAdditional MCP server configuration (JSON string or object). Use @ prefix for file path (e.g., "@config.json")
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only states that the tool delegates tasks, but does not mention any side effects, required permissions, error handling, or safety considerations (e.g., that it can modify code or access files). This is insufficient for a powerful batch tool.

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 consists of two short sentences that directly state the tool's function and ideal use cases. No wasted words; every sentence is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 15 parameters and no output schema, the description is too minimal. It does not cover important aspects like resume capability, parallel execution, tool control, or failure behavior, leaving the agent without key contextual information.

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 the baseline is 3. The general description adds no additional parameter-level meaning beyond what is in the schema, nor does it explain parameter interactions or provide usage examples.

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 the verb 'Delegate' and identifies the resource 'multiple atomic tasks to GitHub Copilot CLI', with examples like 'repetitive operations, mass refactoring'. This distinguishes 'batch' from sibling tools like 'ask' or 'review', which are single-turn interactions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Ideal for repetitive operations' implies a usage context, but the description does not explicitly state when to prefer this tool over alternatives, nor does it mention when not to use it. No exclusions or alternative tools are referenced.

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/x51xxx/copilot-mcp-server'

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