Skip to main content
Glama
Pyrogenesis Fair Player MCP

Pyrogenesis Fair Player MCP

by yunqinglt

analyze_terrain_region

Analyzes visible or previously observed terrain as compact row-major arrays, returning height, slope and approximate building-footprint elevation statistics to assess candidate building sites while keeping unknown samples null.

Instructions

Analyze visible or previously observed terrain as compact row-major numeric arrays.

Returns height, slope and approximate building-footprint elevation statistics. Only player-view terrain is used; unknown samples remain null. A favorable score does not guarantee a legal building location: placement rules, obstructions and native checks are still authoritative.

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": {
      "x_min": "<x_min>",
      "z_min": "<z_min>",
      "x_max": "<x_max>",
      "z_max": "<z_max>",
      "footprint_width": "<footprint_width>",
      "footprint_depth": "<footprint_depth>"
    },
    "name": "analyze_terrain_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_maxYes
x_minYes
z_maxYes
z_minYes
cell_sizeNo
footprint_depthYes
footprint_widthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the data source restriction ('only player-view terrain is used'), null semantics for unknown samples, what statistics come back, and that placement rules and native checks remain authoritative. It never explicitly states that the call has no side effects or what the cost/latency profile is, which is the remaining gap for a zero-annotation tool.

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 core action and output format, then the data-source constraint, then the legality caveat — a sensible order. Four short sentences with essentially no filler; only minor tightening is possible.

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

Completeness2/5

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

The description partly compensates for the absent output schema by naming the returned statistics, which is valuable. But with seven undocumented parameters, no annotations, and a required bounding-box plus footprint specification, an agent still cannot construct a correct call from this text — the units and meaning of cell_size and the footprint dimensions are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — all seven parameters are bare titles ('X Min', 'Cell Size', 'Footprint Width'). The description mentions 'footprint' only in the context of the returned statistics, and says nothing about the coordinate system, units, what cell_size controls, or how footprint_width/depth affect the computation. For six required numeric parameters this is a significant miss.

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?

States a specific verb and resource ('Analyze ... terrain') and immediately names the output shape: compact row-major numeric arrays with height, slope and building-footprint elevation statistics. That is far more than a restatement of the name. It does not explicitly contrast itself with observe_map_region, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Analyze visible or previously observed terrain' implies the precondition (terrain must have been seen) but never states when to pick this over the sibling observation tool. The closing caveat that a favorable score does not guarantee a legal building location is a genuinely useful usage boundary, keeping it above a bare 2.

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