Skip to main content
Glama

check_campaign

Validates a campaign's chapters, maps, images, numbering, and mode coverage against referenced files, reporting missing assets and an overall verdict.

Instructions

Checks a campaign against the files it references: every chapter's .bsp exists in a maps directory or in a VPK, every chapter image exists under materials/vgui, chapter numbering has no gaps, and every mode has chapters. Reports findings and an overall verdict; it does not refuse. The game's own campaigns can be checked in place by passing vpk: left4dead2/pak01_dir.vpk and the mission entry.

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

Input Schema

NameRequiredDescriptionDefault
vpkNoVPK holding the mission, e.g. pak01_dir.vpk.
pathNoMission .txt on disk.
vpksNoFurther VPKs whose entries count as present.
entryNoEntry inside the VPK, e.g. missions/campaign1.txt.
mapsDirsNoDirectories holding <map>.bsp. Defaults from the mission's location.
materialsDirsNomaterials/ directories. Defaults from the mission's location.

Output Schema

NameRequiredDescriptionDefault
modesYes
countsYes
sourceYes
checkedYes
overallYes
findingsYes
chapterCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.4/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 load, and it delivers: it discloses that the tool reports findings plus an overall verdict and explicitly does not refuse, which matters for an agent that might expect a thrown error. It never states outright that the operation is non-mutating, but 'checks' and the enumerated read-only assertions make that clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and the full checklist, followed by the verdict semantics and a practical example. No filler or redundancy.

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?

For a six-parameter, zero-required validation tool with an output schema, the description covers what is validated, how failures are surfaced, and one realistic invocation. It could be slightly more complete about how `path` versus `vpk`+`entry` are chosen and what happens with an empty parameter set.

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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning by pairing `vpk` with the mission `entry` in a worked example and by tying mapsDirs/materialsDirs to the file types they hold. The path-vs-vpk selection for `path` is left implicit.

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 gives a specific verb and resource and then enumerates the exact invariants checked: .bsp presence in a maps dir or VPK, chapter images under materials/vgui, gap-free chapter numbering, and chapters per mode. That enumeration distinguishes it from read_campaign and check_vmf_rules 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a concrete usage scenario for checking the game's own campaigns in place via `vpk: left4dead2/pak01_dir.vpk` plus the mission entry, and clarifies the tool reports rather than blocks. It stops short of stating when to prefer this over check_vmf_rules or read_campaign.

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