Skip to main content
Glama

health

Check the Left 4 Dead 2 toolchain state: repo root, game bin directory, compilers, FGD files, Python srctools install, and served tool count, to find missing dependencies or a stale build.

Instructions

State of the Left 4 Dead 2 toolchain this server depends on: repo root, the game's bin directory (which ships with the client, not with srcds), which compilers and .fgd files are present, whether the Python sidecar (srctools) is installed. Also how many tools this server is serving and whether its build is older than the source -- a stale build silently offers fewer tools. Start here when a tool reports something missing, or is missing itself.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior3/5

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

Annotations supply only a title, so the description carries the full behavioral burden; it does usefully disclose the key trap that a stale build "silently offers fewer tools" and that the bin directory ships with the client rather than srcds. It still never states that the call is read-only and side-effect free, nor how expensive or fast it is.

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?

One dense sentence enumerating the reported fields, followed by a short directive sentence; the purpose is front-loaded and the parenthetical about the client vs. srcds bin directory earns its place as diagnostic context. The enumeration is long but every item is a real field the agent may need to interpret.

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 no parameters and no output schema, the description must describe return content itself, and it does so by listing the checks performed. It is nearly complete, though it does not indicate the response format for missing items or how staleness is determined.

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 convey and the baseline of 4 applies. The description's field enumeration describes output content rather than inputs, which is appropriate here.

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 the concrete resource (Left 4 Dead 2 toolchain state) and enumerates exactly what it reports: repo root, game bin directory, compilers, .fgd files, srctools sidecar, served tool count, and build freshness. An agent can immediately distinguish this diagnostic from the map/VMF/BSP editing siblings.

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?

It gives an explicit trigger: "Start here when a tool reports something missing, or is missing itself," which is clear routing guidance for a diagnostic tool. It stops short of saying when not to use it or naming alternative diagnostics, so it falls short of a 5.

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