Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub health check

github_doctor
Read-onlyIdempotent

Runs a one-screen health check of the server’s token, identity, proxy reachability, cache, and quota; use it to diagnose wiring issues before GitHub requests.

Instructions

One-screen health check of this server's own wiring: token presence, opt-in identity, proxy mode with a TCP reachability probe of the resolved proxy, local cache state, and current quota. Costs 1 core call. Returns {token{present}, identity?{authenticated_as, scopes}, proxy{mode, url, reachable}, cache{mode, dir, entries, bytes}, quota{core{limit, remaining, reset}, search{limit, remaining, reset}}, meta{cache}}.

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": "github_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered; the description adds genuinely new behavior: it costs 1 core call and it performs a live TCP reachability probe of the resolved proxy, which implies network latency and possible failure/hang modes. It stops short of describing what happens when the probe fails or times out, keeping it from a 5.

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?

Dense but front-loaded: what it checks, then cost, then return shape, in three clauses with no filler. The return-shape brace expansion is verbose, but it is earning its place because there is no output schema.

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

Completeness5/5

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

With no parameters, no output schema, and annotations covering the safety profile, this description closes every remaining gap: it enumerates the checks, states the cost, and inlines the return structure including optional identity and quota sub-fields. An agent knows what it will get and what it will spend.

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 meaning to add; the baseline for a no-param tool is 4. The description does not waste space restating an empty input schema.

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 names a specific verb and resource — a health check of 'this server's own wiring' — rather than of GitHub repo data, and enumerates exactly what is checked (token presence, identity, proxy reachability, cache, quota). That enumeration makes it distinguishable from repo-oriented siblings like github_repo_health and from the narrower github_rate_limit without needing to name them.

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 by the content (diagnose connectivity/auth/configuration problems, or check quota) and the 'Costs 1 core call' note gives useful invocation economics, but there is no explicit when-to-use/when-not guidance or a pointer to github_rate_limit for the quota-only case.

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