kazaplan-mcp

Overview Schema Source Related Servers Discussions Admin

Kz Add Pool

kz_add_pool

Adds an inground pool defined by a 2D contour of points, with adjustable height, water depth and coping thickness, to extend a Kazaplan 3D home design.

Instructions

Ajoute une piscine enterrée de contour points ([[x, y], …], cm).

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_pool"
  }
}

Input Schema

Name	Required	Description	Default
`height`	No
`points`	Yes
`water_depth`	No
`coping_thickness`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioural burden. It implies a mutation (adding an object) but says nothing about whether a plan must be open, what happens on overlapping or invalid contours, or whether the pool is immediately committed or undoable — only the unit and point format are disclosed.

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?

One short sentence with no filler, and the essential information (shape format and unit) is packed into it. It is efficient, though its brevity is part of the under-specification problem rather than a virtue in itself.

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?

An output schema exists so return values need not be explained, but for a mutating, object-creating tool with no annotations and three of four parameters undocumented, the description leaves the agent guessing about units, defaults, and required preconditions. It is not adequate for the tool's complexity.

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 four parameters, and the description only explains `points` (array of [x, y] pairs, in cm). The three optional parameters — height, water_depth, coping_thickness — are entirely undocumented in both schema and description, including what units their defaults (100/95/30) are in.

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 gives a concrete verb and resource in 'Ajoute une piscine enterrée' and specifies the geometry is defined by a `points` contour in centimetres. It does not differentiate this from sibling creation tools such as kz_add_opening, kz_add_walls, or kz_place, so it stops short of a 5.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g. an active room or plan must exist), and no exclusion conditions. The agent must infer all routing from the tool name alone.

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