Skip to main content
Glama
Sign In
Copilot Counterpart

Copilot Counterpart

by dstkwll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

copilot_models

List models available through Copilot authentication to identify which ones you can route coding tasks to; no inference request is sent.

Instructions

List models available through your Copilot authentication. No inference request.

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_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses two traits an agent would otherwise have to guess at: the call depends on Copilot authentication, and it triggers no inference request (so no model invocation cost). It does not state rate limits, whether results are cached, or anything about the shape of the response.

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?

Two short sentences, with the core action front-loaded and the disambiguating constraint ('No inference request') placed immediately after. Nothing is redundant or padded.

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

Completeness3/5

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

For a zero-parameter discovery tool this is close to adequate, but with no output schema the description is the only place a caller could learn what each listed model carries (identifiers, capabilities, availability). It says what the tool returns only at the level of 'models', leaving the agent to discover the usable fields at call time.

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 no parameter semantics to explain and the baseline is 4. The description correctly implies no filtering or pagination inputs exist.

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?

States a specific verb and resource: 'List models available through your Copilot authentication.' An agent can tell this is a discovery/enumeration tool, and the 'No inference request' clause separates it from inference-invoking siblings such as copilot_start or copilot_orchestrate, though no sibling is named explicitly.

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?

'No inference request' implies this is the cheap metadata lookup to call before selecting a model, which is useful implied guidance. However, it never states when to prefer this over alternatives or what a caller should do with the returned model list, so the routing guidance is inferred rather than explicit.

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