kazaplan-mcp

Overview Schema Source Related Servers Discussions Admin

Kz Add Opening

kz_add_opening

Adds a door or casement window opening to a wall in a 3D plan, with optional size, elevation, and offset settings to place it precisely.

Instructions

Ajoute une ouverture sur un mur. kind : "door" (90×215 par défaut) ou "casement-window" (100×135, allège 95). offset : distance en cm entre le début du mur et le bord de l'ouverture (sinon centrée).

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": {
      "wall_id": "<wall_id>"
    },
    "name": "kz_add_opening"
  }
}

Input Schema

Name	Required	Default
`kind`	No	door
`width`	No
`height`	No
`offset`	No
`wall_id`	Yes
`elevation`	No
`nb_casement`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose real mutation semantics: sensible default dimensions per kind (90×215 for doors, 100×135 with a 95 cm sill for windows) and default centering. It omits failure behavior (unknown wall_id), unit expectations for width/height, and whether existing openings constrain placement.

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?

Compact and front-loaded: the action comes first, then per-kind defaults, then offset semantics. The embedded dimension notation ('90×215', 'allège 95') is dense but earns its place as default documentation.

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?

A 7-parameter mutation tool with zero annotation coverage and no schema descriptions needs more than this; notably elevation and nb_casement are entirely unexplained, which matters for a tool that places multi-pane windows. The presence of an output schema excuses the lack of return-value documentation, but the input side remains under-described.

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% across 7 parameters, so the description must compensate and only partially does: it explains kind values/defaults and offset (cm from wall start, else centered). width, height, elevation, and nb_casement are never mentioned, leaving over half the parameters without any semantic explanation 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+resource: 'Ajoute une ouverture sur un mur', and immediately distinguishes the two opening kinds ('door' vs 'casement-window') with their default sizes. It stops short of differentiating from siblings (e.g., kz_add_walls) or explaining how openings relate to the wall they attach to.

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 useful defaults that imply usage: kind defaults to 'door', offset omitted means the opening is centered on the wall. However, it never states preconditions (the wall must already exist, wall_id required) or when to choose a window vs a door, so guidance is implied rather than explicit.

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