Skip to main content
Glama
Sauerbraten MCP
by pastukhov

geometry_fill

Destructive

Replaces an aligned selection with solid or empty cubes to fill or clear Sauerbraten level geometry; set cell count, world-unit grid, origin, and orientation.

Instructions

Replace an aligned selection with solid or empty cubes. count is in cells, grid in world units.

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": {
      "request_id": "<request_id>",
      "map_epoch": "<map_epoch>",
      "expected_revision": "<expected_revision>",
      "selection": "<selection>",
      "mode": "<mode>"
    },
    "name": "geometry_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
map_epochYes
selectionYes
request_idYes
texture_refNo
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is supplied externally. The description adds only the replacement outcome and unit semantics; it does not explain revision guarding, map epoch constraints, request_id behavior, texture_ref effects, or what 'empty' does to existing cubes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences with no wasted wording. The first sentence establishes the operation and the second adds targeted unit clarification.

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?

For a complex destructive operation with six top-level parameters, nested selection fields, no output schema, and no schema descriptions, the definition is too thin. It gives purpose and two unit hints but omits critical operational context such as concurrency/revision semantics, texture behavior, and when this tool should be chosen over sibling geometry tools.

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 should compensate heavily. It clarifies only that count is in cells and grid is in world units, leaving map_epoch, expected_revision, request_id, texture_ref, selection.origin, selection.orient, and mode semantics largely unexplained.

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 ('Replace') and resource ('aligned selection') with clear outcome ('solid or empty cubes'). An agent can understand the core operation, but the description does not explicitly distinguish it from sibling geometry tools such as geometry_face_set or geometry_vertex_set.

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?

Provides no when-to-use or when-not-to-use guidance and names no alternatives. The operation is implied by the name and description, but an agent must infer when this fill operation is preferable to neighboring geometry operations.

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