Skip to main content
Glama

sew_displacements

Welds displacement seams in a VMF by pulling matching edge vertices to their shared average position, fixing split geometry before compile.

Instructions

Pulls displacements back together along the edges they share. Two vertices belong together when their undisplaced positions coincide -- the faces share that point whatever either grid has since done to it -- and each group is moved to its average, which is what Hammer's Sew does and what keeps a ridge from being dragged to one side of the join. The check is exact: read_displacements must report no seam afterwards, and it decides adjacency the same way, so it would find any pair this missed.

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": "sew_displacements"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .vmf, absolute or relative to the repo root.
backupNoCopy the file to <file>.bak before writing. Nothing is copied on a no-op.
dryRunNoCheck and report without writing. Every verification runs either way.
confirmNoRequired (true) to run this tool: it writes or executes.
toleranceNoHow close two flat points must be to count as the same one. Default 0.1. Must be positive: zero would group every vertex of the map into one.

Output Schema

NameRequiredDescriptionDefault
pathYes
writtenYes
nextStepYes
warningsYes
unchangedYes
backupPathYes
seamsAfterYes
verticesMovedYes
worstGapAfterYes
worstGapBeforeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.9/5.0
Behavior4/5

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

With only a title annotation and no safety hints, the description carries most of the behavioral burden and does well: it says vertices are moved to their average, explains why this avoids dragging a ridge to one side, and gives an exact post-check via read_displacements. It stops short of explicitly stating that the .vmf is modified or discussing backup/dryRun consequences, which keeps it from a 5.

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 purpose is front-loaded in the first sentence, and the remaining text explains the matching rule and verification concisely. The middle sentence is dense and could be tightened, but its technical detail is relevant and not redundant.

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?

The description explains the operation, matching logic, and verification requirement, which covers the core complexity of a mutation tool. Because the input schema fully documents the five parameters and an output schema exists, the remaining omission of return-value detail is acceptable; missing explicit usage preconditions is the main gap.

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 description coverage is 100%, so every parameter is already documented in the input schema. The description adds conceptual context about adjacency and exact checking but does not clarify path, backup, dryRun, confirm, or tolerance semantics beyond what the schema provides, making the baseline 3 appropriate.

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?

The description opens with a specific verb and resource: "Pulls displacements back together along the edges they share." It clearly identifies the operation as a displacement-sewing action and explains the grouping criterion, so an agent can distinguish it from a read-only sibling like read_displacements.

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?

The description implies the tool is used to repair seams and says read_displacements must report no seam afterwards, which gives a verification workflow. However, it does not explicitly state when to use this tool versus alternatives such as align_faces or move_vertices, nor does it name when-not-to-use conditions.

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