Skip to main content
Glama

read_pakfile

Lists contents of a compiled .bsp's lump 40 ZIP by extension and size to audit packing and verify buildcubemaps and static prop lighting before release.

Instructions

What a compiled map actually ships inside it: lump 40 is a plain ZIP, and this lists its contents by extension and by size. Use it to audit packing before release. Two counts answer questions you would otherwise have to trust the compile settings for: c-*.vtf files prove buildcubemaps was run, and .vhv files prove static prop lighting was baked. Needs the Python sidecar; see health.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "read_pakfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .bsp, absolute or relative to the repo root.
limitNoHow many of the largest entries to list.

Output Schema

NameRequiredDescriptionDefault
pathYes
largestYes
returnedYes
fileCountYes
megabytesYes
totalBytesYes
byExtensionYes
cubemapTexturesYesc-*.vtf entries: machine-checkable proof buildcubemaps ran.
staticPropLightingYes.vhv entries: per-vertex prop lighting, baked by vrad -StaticPropLighting.

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?

With only a title annotation and no readOnly/destructive hints, the description carries the full behavioral burden, and it does add real context: the hard prerequisite on the Python sidecar (with a pointer to health) and the meaning of the two derived counts. It does not, however, say what happens when lump 40 is missing or malformed, which for a file-reading tool is a notable omission.

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?

The purpose is front-loaded in the first sentence, followed by the audit use case and then the two diagnostic rules; every sentence earns its place. Slightly dense phrasing ("What a compiled map actually ships inside it:") costs a point on crispness.

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?

The output schema covers return values, and the description adds the prerequisite and the interpretation of key counts, which is the right division of labor. Missing only error/edge-case behavior for a BSP with no pakfile lump.

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 description coverage is 100%, so both `path` and `limit` are already documented in the schema, and the description adds nothing about them. Baseline 3 applies; no syntax or default behavior is repeated or extended.

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 states a concrete verb and resource: it lists the contents of the pakfile lump (lump 40, a plain ZIP) by extension and size. That is specific enough to distinguish it from generic BSP readers, but it never names run_pakfile_extract, the sibling that actually unpacks those entries, so the list-vs-extract boundary is left implicit.

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?

"Use it to audit packing before release" gives a clear usage context, and the two interpretation rules (c-*.vtf => buildcubemaps ran, .vhv => static prop lighting baked) tell the agent what to look for in the result. There are no explicit exclusions or named alternatives, keeping it 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.