Skip to main content
Glama

read_map_report

Judges a compiled .bsp against a budget profile and returns pass, warn, fail, or skipped verdicts per criterion, so agents know whether map limits are acceptable.

Instructions

Judges a compiled map against a budget profile and returns a verdict per criterion, not just numbers. This is the tool that gives an agent a stopping condition: every other reader here answers 'how much', this one answers 'is that enough'. Covers lump fill against vbsp's ceilings, entity count against the edict budget, LIGHTING against MAX_MAP_LIGHTING, whether vvis ran at all, how finely the world is split, and whether cubemaps and HDR exist. Limits come from Valve's headers; thresholds come from the profile and each one states its own provenance, including when it was simply chosen. A criterion nothing calibrates reports 'skipped' with the reason rather than a confident verdict about nothing.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .bsp, absolute or relative to the repo root.
profileNoBudget profile id. 'source-stock' (default) asks only whether the map will compile and load, using stock Source 2013 ceilings. No L4D2-specific budget has been calibrated yet.
verdictsNoReturn only these verdicts. Omit for all of them.

Output Schema

NameRequiredDescriptionDefault
pathYes
overallYes
profileYes
summaryYes
criteriaYes
filteredOutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A4.2/5.0
Behavior3/5

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

Annotations supply only a title, so the description must carry the behavioral load; it does disclose a lot about output semantics - per-criterion verdicts, 'skipped' with reason when nothing calibrates a criterion, provenance attached to each threshold, and that limits come from Valve's headers. It does not state that the call is read-only, whether it re-parses the .bsp each time, or any cost/latency expectations.

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 core claim is front-loaded and the criteria list is compact and useful. Some rhetorical padding - 'a confident verdict about nothing' - and the meta-commentary about other readers cost a little density without hurting comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and full param coverage, the description supplies what the schema cannot: the six criteria being judged, the default budget posture ('source-stock' asks only whether the map will compile and load), and the honest fallback to 'skipped'. An agent knows when to call it and how to interpret a null-ish verdict.

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 earns one more by clarifying what the profile actually supplies ('thresholds come from the profile and each one states its own provenance') and what a 'skipped' verdict means for the verdicts filter. It adds no detail on path resolution beyond what the schema already says.

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 ('Judges a compiled map against a budget profile') plus the output shape ('a verdict per criterion, not just numbers'), and explicitly differentiates itself from the sibling readers: 'every other reader here answers how much, this one answers is that enough.' An agent can pick it over read_bsp_info or read_lightmap_budget without opening a 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 a clear selection rule ('This is the tool that gives an agent a stopping condition') and scopes it to compiled maps, implying it is a post-compile judgment step rather than a measurement read. It stops short of naming a specific sibling to use instead for raw numbers, so the exclusion is by category rather than by name.

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