Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_view_mode

Retrieves the current garden editor view mode (2D or 3D) so AI assistants can adapt design actions and rendering decisions to the active perspective.

Instructions

Get the current view mode (2d or 3d)

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": "get_view_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return values (2d or 3d), which is useful, but it does not explicitly state that the operation is read-only, side-effect-free, or free of authentication requirements. For a simple getter this is acceptable but not rich.

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 a single, front-loaded sentence with zero unnecessary wording. It fits the simplicity of the tool and gives the key information immediately.

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?

Given the tool's simplicity, no parameters, and no output schema, the description is nearly complete: it states what is returned and the possible values. It could add an explicit read-only note, but nothing essential is missing for an agent to call it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description correctly implies no input is needed by describing only a retrieval operation, and there are no parameters whose meaning could be expanded.

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 clearly states a specific verb and resource: 'Get the current view mode.' It also names the possible values (2d or 3d), which distinguishes it from the sibling set_view_mode and makes the tool's purpose immediately understandable.

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 implied by the getter nature of the tool and its obvious pairing with set_view_mode, but the description does not explicitly say when to use this tool versus alternatives or mention any preconditions. It is minimally adequate for a simple read operation.

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