Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_version

Returns MCP server and connected browser editor version details so you can confirm at session start that the build supports the features you rely on.

Instructions

Returns version info for the MCP server and the connected browser editor. Use at session start to confirm you are talking to a build that supports the features you depend on (e.g. M25 plant-attribute search). Response: { mcpServer: { name, version }, editor: { version, buildTime, gitHash } | null }. The editor block is null when the browser is not connected.

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_version"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.1/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: 'Returns' establishes a read-only operation, the response shape is spelled out, and the null editor case is explained. It does not explicitly say the call has no side effects, nor does it discuss auth or rate limits, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the purpose, then the usage rule, then the return shape. The parenthetical M25 example earns its place by making the 'supports the features you depend on' check concrete.

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?

There is no output schema, so describing the return object (mcpServer name/version, editor version/buildTime/gitHash, nullable editor) is exactly the right compensation. The only gap is the absence of any cross-reference to connection_status, which matters given how similar the two tools' names are.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly does not waste space restating a nonexistent input.

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?

The description uses a specific verb and resource: it 'Returns version info for the MCP server and the connected browser editor.' That is clear and distinct from most siblings, but it never differentiates itself from the nearby connection_status tool, which an agent could plausibly pick instead.

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 gives an explicit when-to-use rule: 'Use at session start to confirm you are talking to a build that supports the features you depend on.' It does not state when not to use it or mention connection_status as the alternative for connectivity checks, so the routing guidance is clear but incomplete.

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