Skip to main content
Glama
Sign In
Copilot Counterpart

Copilot Counterpart

by dstkwll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

copilot_jobs

Lists jobs owned by this server instance so you can inspect current work; it does not start, run, or queue new jobs.

Instructions

List jobs owned by this server instance; does not start work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "copilot_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose the non-mutating nature ("does not start work"), which is the key safety fact for an agent. It says nothing about job states included, ordering, pagination, or result size for a potentially unbounded list.

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?

A single short sentence with the resource first and the negative constraint second; no filler and nothing to trim.

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 a zero-parameter read tool with no output schema, the definition covers what is listed and whose jobs they are, which is most of what an agent needs to select it. Minor gaps remain around whether finished jobs appear and how results are ordered or bounded.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. The instance-scoping note correctly implies no filtering arguments are needed.

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?

Specific verb and resource ("List jobs") plus an explicit scope ("owned by this server instance"). The clause "does not start work" implicitly separates it from copilot_start/copilot_delegate, though no sibling is named outright.

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?

Usage is implied: call it to enumerate jobs on this instance, and it is explicitly not for launching work. There is no explicit routing to an alternative (e.g., "use copilot_start to launch"), and no guidance on when listing is preferable to copilot_events or copilot_changes.

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