Skip to main content
Glama

Copilot bridge diagnostics

copilot_status
Read-onlyIdempotent

Check Copilot setup, version, auth hint, session state, and bridge release status before debugging 'not found' errors; consumes no quota.

Instructions

Check the Copilot setup. Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks copilot's version, an auth hint (copilot has no login-status command, so a credential-store login is assumed unless an env token is set), and where copilot keeps session state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.4

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world, so safety is covered structurally. The description adds genuinely new behavior: zero quota consumption, the inference that login is assumed unless an env token is set (because copilot has no login-status command), and the interpretation rule that a newer release should be surfaced to the user.

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?

Purpose is front-loaded in the first clause, followed by the trigger condition, then the diagnostics inventory. It is dense but each sentence carries information; only the embedded instruction to "tell the user" is arguably advisory rather than definitional.

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?

With an output schema present and no parameters, the description only needs to frame interpretation, which it does for the version and auth rows. The one gap is that it does not mention the session-state location's significance beyond naming it, but overall it is complete for a diagnostic tool of this simplicity.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. No misleading parameter language is present.

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?

States a specific verb and target ("Check the Copilot setup") and then enumerates exactly what it inspects: bridge version, copilot version, an auth hint, and where session state lives. That enumeration makes it distinguishable from the copilot_ask/copilot_continue siblings, which perform work rather than diagnose.

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?

Gives a concrete trigger: run it first when a call reports "not found", and notes it costs no quota so it is safe to invoke preemptively. It does not state any exclusion or name an alternative tool, so it falls just short of fully explicit routing.

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