Skip to main content
Glama
Sign In
Copilot Counterpart

Copilot Counterpart

by dstkwll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

copilot_start

Starts a context-only job on an explicit GitHub Copilot model, bypassing automatic routing. Sends your prompt, returns immediately; poll events for the result.

Instructions

Advanced: start a context-only job on an explicit model, bypassing routing. Sends supplied prompt to GitHub Copilot and consumes its allowance. Requires sharingAuthorized like the routed tools. Optional files grants scoped reads and staged writes; no commands. Supply only task-relevant, non-secret context. Returns immediately; poll copilot_events until terminal. Reuse requestId only for identical retries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "requestId": "<requestId>",
      "prompt": "<prompt>",
      "sharingAuthorized": "<sharingAuthorized>",
      "model": "<model>"
    },
    "name": "copilot_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOptional scoped file access for the delegate. Omit for context-only jobs.
modelYes
promptYes
requestIdYes
timeoutSecondsNo
reasoningEffortNo
sharingAuthorizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the call consumes Copilot allowance, requires authorization, is asynchronous ('returns immediately'), and must be polled via copilot_events until terminal. It also explains the write staging model ('nothing reaches disk until copilot_apply') and the idempotency contract for requestId.

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?

Front-loads the distinguishing framing ('Advanced: ... bypassing routing') before preconditions, file-scoping, and the async polling contract. Dense but nearly every clause carries operational information; a short list format could have made the lifecycle and retry rules even easier to scan.

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?

For an async, no-output-schema tool it covers the essentials: prerequisites, side effects, staged writes, return-immediately behavior, and the exact polling sibling. The unaddressed timeoutSeconds semantics are a small gap given that the call returns immediately, which makes the meaning of a job timeout non-obvious.

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

Parameters4/5

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

Schema description coverage is only 14%, so the description must compensate, and it adds real meaning for model (explicit model selection bypassing routing), sharingAuthorized, files (scoped reads plus staged writes, 'no commands'), and requestId (retry-identity semantics). It says nothing about timeoutSeconds or reasoningEffort, leaving two parameters undocumented in both places.

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?

Names a specific verb and resource ('start a context-only job on an explicit model') and immediately distinguishes itself from sibling behavior with 'bypassing routing' and 'context-only', which separates it from the routed delegate sibling. An agent can tell what this tool does without opening the schema.

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?

Explicitly frames itself as 'Advanced' (implying the routed tools are the default path), states the sharingAuthorized prerequisite, and gives usage constraints for files ('task-relevant, non-secret context') and requestId ('only for identical retries'). It does not name the specific alternative tool an agent should prefer, so the guidance is clear but not fully routing-complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools