Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_units

Configures coordinate input and output units as meters or raw editor units (50 units = 1 m), ensuring spatial values use the correct scale for garden layout and editing.

Instructions

Set the unit system for coordinate inputs/outputs. Default is "m" (meters). When set to "m", all spatial values (x, y, width, height, points) are in meters. When "editor", values use raw editor units (50 units = 1 meter).

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": {
      "unit": "<unit>"
    },
    "name": "set_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes"m" for meters (default, agent-friendly), "editor" for raw editor units (50 = 1m)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.2/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 by disclosing the default value, the affected spatial fields, and the editor conversion rule (50 units = 1 meter). It does not clarify whether the setting is persistent or whether existing stored geometry is re-interpreted, which is a meaningful remaining gap.

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?

The description is three compact sentences with the main purpose and default front-loaded, followed by the relevant unit semantics. There is no unnecessary wording.

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 one-parameter setting tool with no output schema, the description covers the key behavioral context: default, affected coordinate values, and editor conversion. It is nearly complete, though it could mention persistence or the effect on existing state.

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 values are already documented in the schema. The description adds some context about the default and the fields affected, but mostly restates the meter/editor distinction, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Set the unit system for coordinate inputs/outputs.' It clearly scopes the action to coordinate interpretation, which distinguishes it from the sibling read tool get_coordinate_system without ambiguity.

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?

It provides clear context for the two modes and notes that 'm' is the default, which implicitly tells the agent when each value is appropriate. It does not explicitly name alternatives or say when not to use the tool, but the setting is straightforward enough that this is a minor gap.

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

Deploy Server

Other Tools