Skip to main content
Glama

read_source_games

Finds the installed Left 4 Dead 2 game from Steam library and manifest files instead of a hard-coded path, then reports its instance path, FGDs, and available stock compilers.

Instructions

Left 4 Dead 2 as installed here, discovered from Steam's own files rather than from a hard-coded path: libraryfolders.vdf for the libraries, appmanifest_550.acf for the app, and left4dead2/gameinfo.txt for its name, its SteamAppId, its .fgd files and its instance path. Reports which stock compilers are present. This fork supports no other game, so other Source installs are not listed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gameYesThe one profile this fork resolves: l4d2.
noteYes
gamesYes
librariesYes
steamRootsYesDeduplicated by realpath: ~/.steam/steam is usually a symlink.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.6/5.0
Behavior3/5

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

Only a title annotation is present, so the description carries the burden. It does add real context: the data is discovered from Steam's libraryfolders.vdf, appmanifest_550.acf and left4dead2/gameinfo.txt rather than a hard-coded path, and it reports which stock compilers exist. It stops short of stating that it performs no filesystem writes or what the response format is (the output schema covers the latter).

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?

It is compact and information-dense, front-loading the target game and then the file-level provenance. The opening is a noun phrase rather than a verb, and the switching between what it reads and what it reports is slightly dense, but nothing is filler.

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 an output schema present, the definition covers what an agent needs: which game, where the data comes from, and that other Source installs are out of scope. Only read-only status and expected failure modes (e.g., Steam install absent) go unstated.

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?

There are zero input parameters, so there is no parameter meaning to convey and the baseline applies. The description does not waste space restating a nonexistent schema.

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?

The description identifies a specific resource (the Left 4 Dead 2 install, its name, SteamAppId, .fgd files, instance path) and a specific action (discover and report, including which stock compilers are present). It does not lead with an explicit verb, but the scope statement 'This fork supports no other game, so other Source installs are not listed' draws a clear boundary that separates it from other read_* tools.

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 rather than stated: the agent can infer this is the tool to run to locate the game install and learn which compilers exist. The negative case is covered ('other Source installs are not listed'), but no alternatives are named and no explicit 'use this when' trigger is given.

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