Skip to main content
Glama
Sauerbraten MCP
by pastukhov

region_read

Read-onlyIdempotent

Reads octree leaves inside half-open world bounds without subdividing geometry, so you can inspect existing map regions.

Instructions

Read octree leaves in half-open world bounds, without subdividing geometry.

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": {
      "bounds": "<bounds>"
    },
    "name": "region_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
boundsYes
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful trait beyond that: the bounds are half-open and the octree is not subdivided, so no geometry is created as a side effect. It still omits pagination behavior despite a cursor parameter and says nothing about what the read returns.

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?

A single front-loaded sentence with no filler; the 'without subdividing geometry' clause earns its place by preventing a wrong assumption. It is efficient, though its brevity borders on under-specification for a tool with an undocumented cursor.

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?

With only two parameters, no output schema, and no annotation coverage of returns, the description should explain what an octree leaf looks like when returned and how to page with the cursor. Neither is addressed, leaving the agent unable to predict the response shape.

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%, so the description must carry parameter meaning. It clarifies the bounds are 'half-open' world bounds, which the schema does not say, but it never explains the integer 3-vector units, and the 'cursor' parameter is entirely undocumented in both schema and description — a critical gap for a paginated read.

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 verb ('Read') and resource ('octree leaves') scoped to 'half-open world bounds', plus a meaningful restriction: 'without subdividing geometry'. This is distinguishable from the entity/geometry mutation siblings, though the term 'octree leaves' assumes domain familiarity.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus other inspection tools (view_capture, entity_list), no mention of prerequisites, and no indication of when to continue with the cursor. The agent must infer usage entirely from the one sentence.

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