Garden Design MCP Server

set_layer_visible

Show or hide a specific garden rendering layer—plants, buildings, ground, metadata, or map—to inspect surfaces, objects, and zones in the editor.

Instructions

Show or hide a rendering layer

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": {
      "layer": "<layer>",
      "visible": "<visible>"
    },
    "name": "set_layer_visible"
  }
}

Input Schema

Name	Required	Description	Default
`layer`	Yes	Layer name. 'buildings' = architecture objects (furniture, raised beds, planters); 'ground' = surfaces; 'metadata' = zones and pins — hide it to see the surfaces and objects under the zones; 'map' = map background and parcel outline.
`visible`	Yes	Whether to show the layer

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.9.3Nov 6, 2026

TDQS

C2.9/5.0

Behavior2/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 not say whether visibility changes persist in saved project state, whether they affect export or preview captures, or whether the change is immediate in the rendered view. 'Show or hide' implies a view mutation but leaves reversibility, persistence, and side effects entirely undisclosed.

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?

A single front-loaded sentence with no filler or redundancy. It is concise to the point of under-specification, but there is no wasted wording to penalize.

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?

For a two-parameter toggle with a fully documented schema, the essentials for invocation are present. What is missing is contextual framing: persistence of the setting, relationship to get_layer_visibility, and any effect on exports or captures, which matters for a state-changing view tool with no annotations.

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%, and the enum for 'layer' is unusually well documented (including the practical hint that hiding 'metadata' reveals zones and pins' underlying surfaces). The description adds nothing beyond that, so the baseline of 3 is appropriate.

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 specific verb pair ('Show or hide') plus the resource ('rendering layer'), which tells an agent exactly what the tool does. It does not distinguish itself from the sibling get_layer_visibility or set_view_mode, so an agent must infer the read/write split from the names alone.

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 explicit when-to-use guidance, no when-not guidance, and no mention of the obvious alternative, get_layer_visibility. An agent can infer usage from the name, but nothing in the text explains which situations call for this tool versus the companion read-only tool.

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

Deploy Server