Skip to main content
Glama

read_campaign

Reads a Left 4 Dead 2 campaign file or VPK mission entry, returning the mission block, modes, and numbered chapters with maps, display names, and images.

Instructions

Reads a Left 4 Dead 2 campaign file: the mission block, its modes (coop, versus, survival, scavenge) and each mode's numbered chapters with the map, display name and image. Accepts a .txt on disk, or a vpk plus the entry inside it -- the game's own campaigns live in left4dead2/pak01_dir.vpk under missions/. Unknown keys and nested blocks are kept, so a later write does not silently drop them.

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

Input Schema

NameRequiredDescriptionDefault
vpkNoPath to a .vpk, when the mission lives inside one.
pathNoPath to the mission .txt, absolute or relative to the repo root.
entryNoEntry inside the VPK, e.g. missions/campaign1.txt.

Output Schema

NameRequiredDescriptionDefault
nameYes
imageYes
modesYes
sourceYes
modeNamesYes
chapterCountYes
displayTitleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.1/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the disclosure burden and does real work: it declares the preservation guarantee that "unknown keys and nested blocks are kept, so a later write does not silently drop them" — a non-obvious trait that matters for round-tripping with write_campaign. It does not cover failure behavior (missing file, bad VPK entry) or encoding, which keeps it off 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?

Front-loaded with the read purpose and payload shape, then the two input modes, then the preservation caveat — a sensible escalation with no filler sentences. The middle sentence is dense with parenthetical detail, which slightly taxes scanning but every clause carries information.

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?

An output schema exists, so return values need no explanation, and the description covers what an agent needs to pick an input mode and to understand the preservation semantics for later writes. Missing only edge-case behavior on invalid paths or VPK entries for a 3-param, zero-required tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented in the schema, giving a baseline of 3. The description adds genuine meaning beyond that by establishing that `vpk` and `entry` are used together as an alternative to `path`, and by pointing at the game's own VPK as a concrete example — useful but not syntax-level detail.

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 resource ("Reads a Left 4 Dead 2 campaign file") and immediately enumerates the structure returned: the `mission` block, the four modes, and each mode's numbered chapters with map, display name and image. That is enough to distinguish it from write_campaign and check_campaign without opening any schema.

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 concrete mode-selection guidance: pass a `.txt` on disk, or a `.vpk` plus the `entry` inside it, and even points to `left4dead2/pak01_dir.vpk` under `missions/` as the canonical example. It stops short of naming an alternative such as check_campaign or saying when not to use this tool, so it is clear context without explicit exclusions.

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