Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

import_state

Load zones and pins from a JSON state object to restore a saved garden layout or initialize a new design.

Instructions

Import zones and pins from a JSON state object

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": {
      "state": "<state>"
    },
    "name": "import_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState object with zones and pins arrays

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

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 burden of behavioral disclosure, but it only says what is imported. It does not disclose whether existing zones and pins are replaced or merged, whether the operation is destructive, how validation errors are handled, or what the tool returns.

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 unnecessary wording. It is efficient and easy to scan, though the terseness contributes to broader specification gaps rather than being a conciseness defect.

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?

For a state-mutating import with a nested object parameter, no annotations, and no output schema, the description is too sparse. An agent cannot tell whether this replaces current state, merges into it, or what constraints apply.

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 nested schema already documents the state object with pins and zones arrays. The description adds no meaning 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?

States a specific verb ('Import') and resources ('zones and pins') plus the source format ('JSON state object'). It is clear what the tool does, but it does not distinguish itself from the obvious sibling export_state or explain how it relates to get_full_state.

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?

Usage is only implied by the word 'Import' and the JSON state object source. There is no explicit guidance on when to use this versus add_zones, add_pins, or get_full_state, and no mention of prerequisites or when not to use it.

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