Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_object

Modify a garden object's position, size, rotation, or label, or swap its product by ID or name search. Plants and buildings adopt catalog dimensions while ground shapes keep their form.

Instructions

Update a garden object's position, size, rotation, or swap its product. To swap product: pass productId or productQuery. Plants/buildings get new dimensions from catalog; ground shapes keep their shape and only swap texture.

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": {
      "id": "<id>"
    },
    "name": "update_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoNew center X — units determined by set_units (default 'm')
yNoNew center Y — units determined by set_units (default 'm')
idYesObject ID to update
labelNoNew label
widthNoNew width — units determined by set_units (default 'm')
heightNoNew height — units determined by set_units (default 'm')
rotationNoNew rotation in degrees
elevationNoNew elevation in meters — ground surfaces only; architecture keeps its catalog height
productIdNoNew product ID — swaps the product. Plants/buildings adopt new catalog dimensions; ground shapes keep shape and swap texture only.
productQueryNoProduct name search — resolved to productId. Use this OR productId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose a non-obvious side effect: swapped productIds cause plants/buildings to adopt catalog dimensions while ground shapes only retexture, and elevation applies to ground surfaces only. It still omits whether updates are destructive, whether undo (a sibling tool) can revert them, and what happens on an invalid id.

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?

Two tight, front-loaded sentences with zero filler; the primary operation comes first and the product-swap nuance follows. Minor redundancy with the schema's productId wording keeps it from a 5.

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?

Ten parameters with no annotations and no output schema: the description covers the geometry and product-swap paths well, and the schema covers units and elevation detail. However, it says nothing about the return value (success vs. updated object state), error behavior for a bad id, or interaction with undo, which an agent needs before calling a mutation tool.

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%, so the baseline is 3. The description largely restates the schema's own productId/productQuery text (including the 'this OR that' constraint) rather than adding new format or unit semantics beyond what the properties already document.

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 ('Update') and resource ('a garden object') and enumerates the mutable facets: position, size, rotation, product. It implies single-object scope versus the sibling update_objects, but never explicitly contrasts with it, so it stops short of full sibling differentiation.

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 one piece of in-tool routing guidance — use productId or productQuery to swap a product — but offers no guidance on when to choose this over update_objects (bulk), add_object, or set_units for unit changes. Usage context is implied rather than stated.

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