Skip to main content
Glama
Garden Design MCP Server

Garden Design MCP Server

get_plant_info

Retrieve detailed botanical characteristics, growing requirements, and maintenance schedules for a plant product to compare options and make informed plant selection decisions.

Instructions

Returns detailed botanical information for a plant product: characteristics (height, spread, form, foliage, flowers), requirements (soil, sunlight, hardiness), and maintenance schedule. Use this to make informed plant selection decisions.

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": {
      "productId": "<productId>"
    },
    "name": "get_plant_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesProduct ID of the plant to look up

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 burden. 'Returns' implies a read-only lookup and the description discloses the broad information categories returned, but it does not address error behavior, permissions, or whether the result is cached or live.

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 two sentences, front-loaded with what is returned, then a concise usage note. Every sentence earns its place, and the parenthetical field groups aid scanning without clutter.

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 simple one-parameter lookup with no output schema, the description gives a useful high-level account of returned botanical categories. It is nearly complete, though it could clarify sibling boundaries and failure behavior.

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 coverage is 100% and the single productId parameter is fully documented in the schema. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 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 clearly states a specific verb and resource: it returns detailed botanical information for a plant product, and it names the main content categories. It does not explicitly differentiate itself from overlapping siblings such as get_plant_attributes or get_product_details, so it misses the top tier for sibling differentiation.

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 a clear usage context: 'Use this to make informed plant selection decisions.' However, it does not state when to prefer this tool over get_plant_attributes, get_product_details, or search_plants, nor does it specify exclusions.

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