Garden Design MCP Server

capture_preview

Capture a screenshot of the garden framed on its parcel with a 2 m margin in the current view mode, returning an image for direct review. Switch to 2D for a plan view.

Instructions

Capture a screenshot of the garden framed on the parcel (2 m margin), in the current view mode — switch to 2d with set_view_mode for a plan view. Returns an image you can view directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capture_preview"
  }
}

Input Schema

Name	Required	Description	Default
`maxSize`	No	Optional: image size in pixels (default 1200)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.9.3Nov 6, 2026

TDQS

A3.8/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 disclosure burden. It does useful work by disclosing the 2 m parcel margin, that output depends on current view mode, and that the result is a directly viewable image; it says nothing about cost, whether unsaved edits are reflected, or any permission/side-effect profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and framing, followed by the view-mode caveat and return type. No filler or redundancy.

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?

For a zero-required-parameter tool with no output schema, the description covers what is captured, how it is framed, which view mode applies, and that the return is a viewable image. Only the relationship to unsaved state and to zoom_image remains unstated.

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 100% and the single parameter maxSize already documents its meaning and default of 1200 px. The description adds nothing about the parameter, so the baseline of 3 applies when the schema does all the work.

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 ('capture a screenshot of the garden') plus the exact framing rule ('framed on the parcel, 2 m margin'), which is real information an agent cannot get from the name. It only partially differentiates from the related sibling zoom_image, which also produces imagery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete conditional: the capture uses the current view mode and you should call set_view_mode to 2d first if you want a plan view. That is genuine when-to-do-something guidance, though there is no explicit when-not to use this versus zoom_image or other image-producing siblings.

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

Deploy Server