Skip to main content
Glama
kazaplan-mcp

kazaplan-mcp

by padupuy

Kz Add Walls

kz_add_walls

Add a connected chain of walls through specified points in centimeters, with configurable thickness and height; free ends join existing walls for T or corner connections.

Instructions

Ajoute une chaîne de murs reliés passant par points ([[x, y], …], cm). Épaisseurs usuelles : 30 extérieur, 7 cloison. Une extrémité libre posée sur un mur existant (axe ou face, à ½ épaisseur + 4 cm près) s'y raccorde : en T sur le flanc, en coin sur une extrémité libre. Les faces (wall.pane) des nouveaux murs sont créées par le planner à l'ouverture. Aucune pièce n'est créée : le planner la détecte à la prochaine ouverture + enregistrement, ensuite seulement la nommer avec kz_set_room.

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": {
      "points": "<points>"
    },
    "name": "kz_add_walls"
  }
}

Input Schema

NameRequiredDescriptionDefault
closedNo
heightNo
pointsYes
thicknessNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 well: it discloses the auto-connection logic (free end within ½ thickness + 4 cm of an existing wall snaps as a T on the flank or a corner on a free end), that faces are created later by the planner, and that no room is produced. It omits what happens on invalid point chains or whether existing walls are modified during snapping.

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?

Four front-loaded sentences that each carry useful information — geometry format, thickness conventions, snapping behavior, and the room-creation caveat. Dense but no filler; minor line-break fragmentation is the only structural quibble.

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

Completeness3/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 mutation workflow and snapping semantics are well covered. But for a 4-parameter write tool with no annotations and zero schema description coverage, leaving `closed` and `height` entirely undescribed is a real completeness 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 coverage is 0%, so the description must compensate, and it only partly does: it defines the `points` format ([[x, y], …], cm) and gives typical `thickness` values (30 exterior, 7 partition). The `closed` and `height` parameters are never mentioned, leaving half the parameters undocumented anywhere.

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: adds a connected chain of walls through `points` in cm. It also implicitly separates itself from kz_set_room by noting that no room is created here, though it does not explicitly contrast with other geometry-mutating siblings such as kz_add_opening.

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?

Gives an important sequencing rule (rooms only appear after the next opening + save, and only then can kz_set_room name them) which effectively tells the agent what to do after this call. However it never states when to prefer this tool over alternatives or any prerequisites for calling it.

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