Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_view_mode

Switches the garden plan between 2D top-down and 3D perspective views so you can inspect layout and plant placement from either angle.

Instructions

Switch between 2D (top-down) and 3D (perspective) view

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": {
      "mode": "<mode>"
    },
    "name": "set_view_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesView mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the semantic meaning of each mode, which is genuinely useful. However, it says nothing about whether the setting persists, affects subsequent renders/captures, or requires certain app state, leaving the mutation behavior partly opaque.

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?

One short sentence, front-loaded with the verb and resource and ending with the clarifying glosses for both modes. There is 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 single-enum setter with no output schema, this is nearly complete: the modes are defined and the action is unambiguous. The only missing piece is persistence/return behavior, which is marginal for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single enum is already constrained, so the baseline is 3. The description earns an extra point by explaining what each enum value actually means ('top-down' vs 'perspective'), which the schema's bare 'View mode' description does not.

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 ('Switch') plus the resource (view mode) and immediately defines both enum values as 2D top-down vs 3D perspective, so an agent knows exactly what the tool changes. It doesn't explicitly name its read counterpart get_view_mode, but the verb contrast makes the split obvious.

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?

Usage is only implied: an agent can infer 'call this to change the view' but the description never says when to pick this over get_view_mode or whether the change is persistent across sessions. No exclusions or prerequisites are given.

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