Skip to main content
Glama

Plant Guide: Dubai gardening research

Month-by-month planting calendar

get_planting_calendar
Read-onlyIdempotent

Sow, plant, flower, harvest, prune and feed months for a set of plants (by slug, category or group), as a 12-month grid. Use it to compare timings across several plants.

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

Input Schema

NameRequiredDescriptionDefault
groupNoAll plants of one group (shows the first 60).
slugsNoUp to 30 plants, by slug or name. Omit slugs, category and group for the kitchen-garden vegetables and herbs.
categoryNoAll plants of one category (shows the first 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / group / enum
      Previous value: -[
      -  "vegetables-herbs",
      -  "flowers",
      -  "trees-palms",
      -  "shrubs-climbers",
      -  "lawn-grasses",
      -  "indoor",
      -  "water"
      -]New value: +[
      +  "flowers",
      +  "trees-palms",
      +  "shrubs-climbers",
      +  "vegetables-herbs",
      +  "lawn-grasses",
      +  "indoor",
      +  "water"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered. The description adds the meaningful output shape (a 12-month grid), but omits behavioral traits an agent would care about, such as the 60-result truncation for group/category queries and the default set applied when no selector is given.

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, no filler, with the capability statement front-loaded and the usage hint second. Nothing is wasted.

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-required-param, read-only query with a fully documented schema, the description covers what the tool returns and why you'd use it. The only gap is that the default selection behavior and result cap live solely in the schema rather than the description.

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%, so all three selectors, their enums and the default-to-kitchen-garden behavior are already documented. The description's "(by slug, category or group)" merely restates the selector options without adding syntax, precedence, or combination semantics.

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?

States a concrete resource (planting calendar months for sow/plant/flower/harvest/prune/feed) and the return shape (a 12-month grid), which is more than the title alone conveys. It does not name or contrast with the closest sibling, what_to_plant, so it stops short of a 5.

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?

"Use it to compare timings across several plants" implies a multi-plant comparison scenario, but there is no explicit when-not guidance and no reference to what_to_plant or search_plants as the single-plant alternative. Usage must be inferred from the comparison hint.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources