Skip to main content
Glama

Ask GitHub Copilot (new session)

copilot_ask

Submit a coding question or task to GitHub Copilot CLI in a new session. Returns the agent's final response, using workspace context for relevant answers.

Instructions

Ask the GitHub Copilot CLI (copilot -p) a question or task in a NEW session.

Uses your existing Copilot login (OS credential store, or a COPILOT_GITHUB_TOKEN/GH_TOKEN/GITHUB_TOKEN env var — see copilot_status). Returns the agent's final message, read straight from stdout (the CLI's -s silent mode; no scraping). Copilot is a capable agentic coder — good for real code/repo work; point workspace at a project dir for context-aware answers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional model override (`--model`). Use "auto" to let Copilot pick. Which ids work is ACCOUNT-DEPENDENT and copilot exposes no non-interactive list, so the bridge cannot validate this the way the agy/cursor tools do — an unavailable id errors immediately with copilot's own message, costing a call. Prefer omitting it (your account default) or "auto" unless you know your plan's ids.
watchNoIf true, open a live "watch" view streaming copilot's steps from its `--output-format json` event stream. Same final text is returned. Best-effort. Default false.
promptYesQuestion or instruction for Copilot.
sandboxNoPermission policy (maps to copilot's tool/path flags): "read-only" (default — best-effort: denies the local write/shell tools; NOT an OS sandbox, so unlike codex it is not a hard boundary), "workspace-write" (may edit files, confined to the workspace), or "danger-full-access" (--allow-all — avoid).read-only
timeout_sNoMax seconds to wait for copilot to complete. Default 180. (Copilot's reasoning models can be slow; raise this if needed.)
workspaceNoWorking root for the session (`-C`). Defaults to the server cwd.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate readOnlyHint false, openWorldHint true, idempotentHint false. Description adds useful behavioral details: uses existing login, returns stdout from CLI in silent mode, best-effort watch option, and notes sandbox is not a hard boundary. No contradiction.

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

Conciseness4/5

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

Description is front-loaded with the key action and well-structured, though it could be slightly more concise without losing important details.

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

Completeness4/5

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

Given the tool's complexity (6 params, output schema, siblings), the description covers purpose, usage, parameters, and output. It lacks explicit error handling but is otherwise sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters have schema descriptions (100% coverage), and the description adds context beyond schema, such as explaining model validation limitations, sandbox distinctions from codex, and workspace usage for context-aware answers.

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 'Ask the GitHub Copilot CLI a question or task in a NEW session,' specifying the verb, resource, and distinguishing from sibling tools like copilot_continue.

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 advises using the tool for real code/repo work with workspace context, and mentions alternatives like copilot_status for login. It warns about model validation errors, but could more explicitly say when not to use.

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/SinanTufekci/agent-intern'

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