Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_garden_description

Document a garden's design brief, decisions, rationale, current phase, and next steps in Markdown so plans persist across sessions.

Instructions

Set the garden description (Markdown supported). Use as a design journal — write the brief, key decisions, rationale, current phase, and what's next. Persists across sessions.

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": {
      "description": "<description>"
    },
    "name": "set_garden_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesGarden description in Markdown format (design brief, decisions, rationale). Supports headings, lists, bold, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that content 'persists across sessions' and that Markdown is supported, which is real context beyond the schema. However, it never says whether this replaces or merges with an existing description (the verb 'set' implies overwrite but this is unstated), nor anything about size limits or permissions.

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?

Two sentences, zero filler, with the core action stated first and the content guidance second. Every clause earns its place and nothing is repeated.

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 one-parameter tool with no output schema and full schema coverage, the description covers purpose, intended content, format, and persistence — enough to call it correctly. The main remaining gap is overwrite/merge semantics on repeated calls, which matters for a state-setting 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 description coverage is 100% and the single parameter is already documented as Markdown with headings, lists, and bold. The description's journal content list ('brief, key decisions, rationale, current phase, what's next') adds modest guidance about what to put in the string, but largely overlaps the schema text, so baseline 3 applies.

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 opens with a precise verb+resource ('Set the garden description') and notes Markdown support, which is unambiguous. It does not explicitly differentiate itself from read-side siblings like get_garden_info, but the write intent is clear from the name and first clause.

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 concrete when-to-use guidance — 'Use as a design journal — write the brief, key decisions, rationale, current phase, and what's next' — which tells the agent what content belongs here. There is no when-not guidance or reference to an alternative tool, so it stops short of the top score.

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