Skip to main content
Glama

read_map_geometry

Read a compiled BSP's lump directory to report each lump's size and proximity to vbsp compiler ceilings, revealing what limits map growth before you plan edits.

Instructions

What each lump of a compiled map holds, and how close that is to the compiler's ceiling. Reads only the 1036-byte directory, so it is instant. Limits are vbsp's own, from source-sdk-2013; a map that exceeds one is a map whose compilers raised it, not a broken map. Use it to see what stops a map from growing before planning work on it.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .bsp, absolute or relative to the repo root.
nearLimitOnlyNoReturn only the lumps at or above 80% of their ceiling.

Output Schema

NameRequiredDescriptionDefault
pathYes
lumpsYes
versionYes
fileSizeYes
limitSourceYes
mapRevisionYes
nearLimitCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.9/5.0
Behavior4/5

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

The annotations carry no hints beyond a title, so the description does the behavioral work: it discloses that only the 1036-byte directory is read (hence instant, no costly parsing) and that the limits are vbsp's own from source-sdk-2013. The line clarifying that an over-limit map reflects raised compiler limits rather than corruption is genuinely useful interpretive context. It does not cover failure behavior for a missing or non-.bsp path.

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?

Four short sentences, front-loaded with what is read and how cheap it is before the interpretive caveat and the usage line. The opening clause ("What each lump of a compiled map holds") is slightly oblique for a first sentence but nothing is wasted.

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 an output schema present, return values need no explanation, and the description supplies the cost profile and the correct reading of limit overruns. What remains unsaid — error cases and how this differs from content-inspecting siblings — is minor for a two-parameter read 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 description coverage is 100%, so both `path` and `nearLimitOnly` (including the 80% threshold) are already documented in the schema. The description adds no further parameter semantics, so the baseline of 3 applies.

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 specific resource and scope: the lump directory of a compiled map and each lump's headroom against vbsp's ceilings. The verb is implied rather than front-loaded ("Reads only the 1036-byte directory"), and no sibling such as read_bsp_info or read_lightmap_budget is named as the alternative, so the agent must infer the boundary from the domain framing.

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 a clear trigger: "Use it to see what stops a map from growing before planning work on it," which tells the agent this is a pre-planning diagnostic rather than an inspection of contents. It stops short of stating when not to use it or naming the sibling that reads full lump contents instead.

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