Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_plant_attributes

Retrieves valid plant filter values and numeric ranges for the current locale, helping you choose search criteria that return matching plants before a plant search.

Instructions

Returns the full vocabulary of selectable plant filter values for the current viewer locale: enum lists (flowerColor, bloomPeriod, sunlight, soil, foliageType, foliageColor, maintenanceLevel, form) and observed numeric ranges (height, spread, hardiness). Call this BEFORE search_plants so you pick only valid values; values not in this vocabulary will yield empty results from search_plants. Lazy-loaded once per session and cached.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does well: it reveals lazy loading, one-time fetch per session with caching (implying idempotent, low-cost repeat calls), and locale-dependence of the returned values. It stops short of explicitly stating that the call is side-effect free or describing the exact shape of the range objects, but the mutation-vs-read question is unambiguous from "Returns".

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 sentences, front-loaded with purpose, then the sequencing instruction, then the caching note — a clean descending order of importance. The parenthetical enumeration of filter keys is dense but each item earns its place by telling the agent exactly what keys to expect.

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 zero-param, no-annotation, no-output-schema tool, the description supplies purpose, sequencing, failure mode, and caching behavior. The only gap is that it never spells out the return envelope (e.g. whether ranges are min/max pairs or the full response structure), which an agent consuming the output without an output schema might want.

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 no schema semantics to restate and the baseline is 4. The description correctly spends its words on what the parameterless call yields rather than inventing parameter guidance that does not exist.

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 opens with a specific verb+resource ("Returns the full vocabulary of selectable plant filter values") and then enumerates the exact contents (eight enum lists plus height/spread/hardiness ranges). It is unmistakable against siblings like search_plants or get_plant_info, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit ordering rule — "Call this BEFORE search_plants" — and states the negative consequence of skipping it (invalid values yield empty results from search_plants). This is exactly the when-to-use / why-not-to-skip guidance an agent needs to sequence the two tools correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.