Skip to main content
Glama

read_model_info

Reads a Source .mdl's bounds, skins, sequences and materials so you can check where a prop's origin sits before placing it, avoiding props that sink into the floor.

Instructions

Bounds, skins, sequences and materials of one .mdl -- what Hammer's model viewer shows before you place a prop. The bounds are the reason this exists: a model's origin is wherever the artist put it, so a prop placed at floor height sinks by however far its origin sits above its lowest point, and nothing downstream reports that. A barrel measured here is 52 units tall with its origin at the centre, which means 26 units underground if it is placed on the floor's own z. 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": {
      "model": "<model>"
    },
    "name": "read_model_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoGame profile id. This fork supports only 'l4d2', which is also the default; any other id is refused rather than answered about the wrong game.
modelYesModel path. The models/ prefix and the .mdl suffix are added if missing.

Output Schema

NameRequiredDescriptionDefault
gameYes
maxsNo
minsNo
noteNo
sizeNo
foundYes
modelYes
mountedYes
refusedNo
materialsNo
readErrorNo
sequencesNo
skinCountNo
mountErrorNo
sequenceCountNo
sequencesTruncatedNo

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, the description carries the burden and does disclose real context: the Python sidecar dependency, the single-game restriction, and the origin-vs-floor pitfall that makes the tool non-obvious. It still lacks read-only framing, error modes beyond the game refusal, or any hint about cost/latency of the sidecar call.

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-loads the output facets, then justifies the tool with the origin-offset argument, which is the right ordering. The barrel example is illustrative but costs roughly a third of the text, slightly more than the point requires.

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?

An output schema exists so return values need no explanation, and the description still covers the sidecar requirement and the single-game constraint that would otherwise surprise a caller. What remains missing is guidance relative to the many read_* siblings, but the core call information is sufficient.

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%, so both parameters are already documented, including prefix/suffix normalization and the l4d2-only game default. The description adds no parameter-specific meaning such as path format examples or what happens on a malformed model path, which leaves it at the baseline.

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?

Opens with a specific verb-and-resource statement ('Bounds, skins, sequences and materials of one .mdl') and enumerates the returned facets, which separates it from siblings like read_materials or read_prop_survey. It does not name an alternative tool, so the differentiation is implicit rather than stated.

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 concrete motivation for when to call it: checking a model's origin offset before placing a prop, since 'nothing downstream reports that.' It clears up the primary confusion (why bounds matter) but never says when to skip this tool or which sibling covers related needs.

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