Skip to main content
Glama

read_map_extents

Reads a compiled .bsp map's real extents from its world model, returning bounding box in Hammer units and metres, longest horizontal span, and ground area for accurate level sizing.

Instructions

Real size of a compiled map, from the world model in lump 14. Returns the bounding box in Hammer units and in metres, the longest horizontal span and the ground area. Use this rather than entity origins: those say where things were placed, not how far the world goes. One Hammer unit is one inch (0.0254 m). Instant on any map size.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .bsp, absolute or relative to the repo root.

Output Schema

NameRequiredDescriptionDefault
maxsYes
minsYes
pathYes
sizeUnitsYes
spanUnitsYes
modelCountYesModel 0 is the world; the rest are brush entities.
sizeMetresYes
spanMetresYes
metresPerUnitYes
areaSquareMetresYes

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?

Only a title annotation exists, so the description carries the burden and mostly does: it identifies the data source (lump 14 of the compiled BSP), states the output unit system with the inch/metre conversion, and notes performance ('Instant on any map size'). It leaves implicit that the path must point to a compiled .bsp rather than a .vmf, which matters given siblings like read_vmf.

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 result, followed by usage rule, unit convention, and performance note in four tight sentences. Every sentence earns its place; the 'Real size' phrasing is slightly informal but costs nothing.

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?

A single-parameter read tool with an output schema, so return-value detail is not needed; the description still summarizes what comes back and where it comes from. The main omission is the compiled-vs-source-file precondition, which is relevant given the surrounding VMF tools.

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% and the single path parameter is already documented as absolute or relative to repo root. The description adds nothing about the path beyond what the schema says, so the baseline 3 applies.

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 resource (compiled map extents from the world model in lump 14) and enumerates what it returns: bounding box in Hammer units and metres, longest horizontal span, ground area. An agent can distinguish this from geometry, entity, or info readers in the sibling list 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?

Explicitly says to use this rather than entity origins, with the reason (origins show placement, not world extent), which is a real decision rule. It does not name a concrete sibling tool to prefer or avoid, so it stops short of full routing guidance.

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