Skip to main content
Glama
Sign In

Plant Guide: Dubai gardening research

by ae.plantguide
OverviewDiscussionsAdmin

What to plant in Dubai this month

what_to_plant
Read-onlyIdempotent

What to sow and plant in Dubai in a given month or season, plus what is flowering, fruiting or ready to harvest, the month's verdict, tips, watch-outs and the climate. Defaults to the current month in Dubai. Also returns that month's indoor-plants block (what to buy, pot up and care for indoors) unless you filter to another group. Start here for any 'what should I plant now / in October / in summer' question.

Input Schema

NameRequiredDescriptionDefault
groupNoOnly this kind of plant: vegetables-herbs, flowers, trees-palms, shrubs-climbers, lawn-grasses, indoor (houseplants: the good months to buy and pot up) or water. Omit it to get everything plus the month's indoor block; any group other than indoor leaves the indoor block out.
limitNoMost plants to list per section, 1–50 (default 20). Long lists are sampled across groups; filter by group to see more.
monthNoMonth to plan for: 1–12 or a name like "october". Omit for the current month in Dubai. Not with season.
seasonNoA whole season instead of one month: winter (Dec–Feb), spring (Mar–May), summer (Jun–Sep) or autumn (Oct–Nov). Not with month.

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. Changed1 schema field changed
    • changedInput schema / properties / group / description
      Previous value: -"Only this kind of plant: vegetables-herbs, flowers, trees-palms, shrubs-climbers, lawn-grasses, indoor or water."New value: +"Only this kind of plant: vegetables-herbs, flowers, trees-palms, shrubs-climbers, lawn-grasses, indoor (houseplants: the good months to buy and pot up) or water. Omit it to get everything plus the month's indoor block; any group other than indoor leaves the indoor block out."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world and idempotency, yet the description still adds non-obvious behavior: it defaults to the current Dubai month and silently includes the indoor-plants block only when no group (or group=indoor) is given. That conditional output rule is real value beyond the annotations; return shape and the sampling behavior of limit are left unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and ending with the routing cue; nothing is padding. Slightly dense/packed with enumerated return items, but each clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero required parameters and no output schema, the description carries the burden of telling the agent what comes back — and it does, listing the sections returned plus the default month and the indoor-block rule. An agent can call this correctly from the description alone.

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%, so month/season/group/limit are all documented in the schema already. The description reinforces the group→indoor-block interaction and hints that month accepts names like 'October' or 'summer', but adds no syntax or constraint detail the schema lacks. 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 names a specific verb+resource (what to sow and plant in Dubai for a month/season) and enumerates the payload: flowering, fruiting, harvest, verdict, tips, watch-outs, climate. It stops short of naming the sibling it overlaps with (get_planting_calendar / get_indoor_plant_guide), so differentiation is only implied by 'Start here'.

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?

'Start here for any "what should I plant now / in October / in summer" question' gives a clear triggering condition and example phrasings, and the default (current month in Dubai) is stated. No explicit when-not or named alternative tool, so it falls short of a 5.

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

All Plant Guide: Dubai gardening research toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources