Skip to main content
Glama
x51xxx
by x51xxx

ask

Execute GitHub Copilot CLI for code analysis and task automation with file access, tool control, and session management.

Instructions

Execute GitHub Copilot CLI with file analysis, tool management, and safety controls

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 or Copilot's default
addDirNoAdd directories to allowed list for file access
bannerNoShow the animated banner on startup
logDirNoSet log file directory
promptYesTask or question for GitHub Copilot CLI. Supports @ syntax for files/images (e.g., '@file.png', '@src/') and ! prefix for direct shell commands
resumeNoResume from a previous session (optionally specify session ID)
noColorNoDisable all color output
timeoutNoMaximum execution time in milliseconds
continueNoResume the most recent session
denyToolNoDeny specific tools (takes precedence over allowTool)
logLevelNoSet the log level
allowToolNoAllow specific tools to run. Supports glob patterns (e.g., 'shell(npm run test:*)')
sessionIdNoUse specific session ID for multi-turn conversations
workingDirNoWorking directory for command execution. Falls back to COPILOT_MCP_CWD env var or process.cwd()
screenReaderNoEnable screen reader optimizations
allowAllPathsNoAutomatically approve access to all file paths (use with caution)
allowAllToolsNoAllow all tools to run automatically (required for non-interactive mode)
disableMcpServerNoDisable specific MCP servers
additionalMcpConfigNoAdditional MCP server configuration (JSON string or object). Use @ prefix for file path (e.g., "@config.json")
enableSessionTrackingNoEnable session tracking for conversation persistence
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions 'safety controls' without explaining behaviors, prerequisites, output, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but not front-loaded with the most critical context; it could be more structured while remaining succinct.

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 complexity (20 parameters, many optional), the description lacks critical context about what the tool does interactively, output expectations, and multi-turn support.

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?

The description adds no meaning beyond the input schema, but the schema covers 100% of parameters with their own descriptions, so 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?

The description clearly states it executes GitHub Copilot CLI with file analysis, tool management, and safety controls, but does not differentiate it from sibling tools like 'batch' or 'review'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives; no explicit when/when-not or context is given.

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