Plant Guide: Dubai gardening research

Search the Dubai plant library

search_plants

Read-onlyIdempotent

Search and filter the library of plants rated for Dubai's heat, salt, drought and shade: by name (English, botanical or Arabic), category, sun, water need, minimum tolerance ratings, use, garden style or planting month. For houseplants and questions like "low light, pet friendly plants for a Dubai apartment", filter by light (low, medium, bright-indirect, direct-sun), petSafe, room and size: those four filters return only plants with an indoor profile (light, tolerance of dry air and air conditioning, pet safety, size, rooms). Returns short profiles with links; call get_plant for the full one.

Input Schema

TableJSON Schema

Name	Required	Description
`sun`	No	The plant's light need, exact match: full-sun, sun-part-shade, part-shade or shade.
`use`	No	What the plant is for: shade-tree, specimen, hedge, screen, windbreak, groundcover, lawn, container, climber, pool-side, fragrance, edible, bedding, indoor or native-habitat.
`room`	No	Houseplants that suit this room: living-room, bedroom, bathroom, kitchen, home-office, majlis, hallway or balcony. Using light, petSafe, room or size limits results to plants with an indoor profile.
`size`	No	The houseplant's usual indoor size: tabletop (on a table or shelf), medium (a medium pot on a sideboard or the floor) or floor (floor-standing). Using light, petSafe, room or size limits results to plants with an indoor profile.
`group`	No	Only this group: vegetables-herbs, flowers, trees-palms, shrubs-climbers, lawn-grasses, indoor or water.
`light`	No	Houseplants that grow well in this indoor light: low (a dim room or corner), medium (a bright room, no direct sun), bright-indirect (by a window, out of direct sun) or direct-sun (a sunny window). Using light, petSafe, room or size limits results to plants with an indoor profile.
`limit`	No	Results per page, 1–50 (default 20).
`query`	No	Words to look for in names (English, botanical, Arabic) and descriptions, e.g. "date palm", "غاف", "salt tolerant hedge".
`style`	No	Garden style it suits: tropical, manicured, luxury or desert-modern.
`water`	No	Highest water need you accept: "low" keeps very-low and low.
`offset`	No	How many results to skip, for paging; use the nextOffset from the previous page.
`origin`	No	native (UAE), adapted or exotic.
`minEase`	No	Minimum ease of care, 1–5 (5 = easiest).
`minHeat`	No	Minimum heat tolerance in Dubai, 1–5 (5 = best).
`minSalt`	No	Minimum salt tolerance, 1–5 (5 = best).
`petSafe`	No	true keeps only houseplants that are non-toxic to cats and dogs (ASPCA list); false means pets do not matter. Using light, petSafe, room or size limits results to plants with an indoor profile.
`category`	No	Only these plant categories (any of them): tree, palm, shrub, climber, groundcover, flower, grass, succulent, herb, edible, indoor, fruit-tree, vegetable, ornamental-grass, aquatic.
`minShade`	No	Minimum shade tolerance, 1–5 (5 = best); use for shady spots.
`minDrought`	No	Minimum drought tolerance, 1–5 (5 = best).
`plantingMonth`	No	Only plants with a sowing or planting window in this month (1–12 or a name). For houseplants this is the good months to buy and pot up.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / light

Added value: +{
+  "description": "Houseplants that grow well in this indoor light: low (a dim room or corner), medium (a bright room, no direct sun), bright-indirect (by a window, out of direct sun) or direct-sun (a sunny window). Using light, petSafe, room or size limits results to plants with an indoor profile.",
+  "enum": [
+    "low",
+    "medium",
+    "bright-indirect",
+    "direct-sun"
+  ],
+  "type": "string"
+}

addedInput schema / properties / petSafe

Added value: +{
+  "description": "true keeps only houseplants that are non-toxic to cats and dogs (ASPCA list); false means pets do not matter. Using light, petSafe, room or size limits results to plants with an indoor profile.",
+  "type": "boolean"
+}

changedInput schema / properties / plantingMonth / description

Previous value: -"Only plants with a sowing or planting window in this month (1–12 or a name)."New value: +"Only plants with a sowing or planting window in this month (1–12 or a name). For houseplants this is the good months to buy and pot up."

addedInput schema / properties / room

Added value: +{
+  "description": "Houseplants that suit this room: living-room, bedroom, bathroom, kitchen, home-office, majlis, hallway or balcony. Using light, petSafe, room or size limits results to plants with an indoor profile.",
+  "enum": [
+    "living-room",
+    "bedroom",
+    "bathroom",
+    "kitchen",
+    "home-office",
+    "majlis",
+    "hallway",
+    "balcony"
+  ],
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "The houseplant's usual indoor size: tabletop (on a table or shelf), medium (a medium pot on a sideboard or the floor) or floor (floor-standing). Using light, petSafe, room or size limits results to plants with an indoor profile.",
+  "enum": [
+    "tabletop",
+    "medium",
+    "floor"
+  ],
+  "type": "string"
+}

First observedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower. The description adds a genuinely non-obvious behavioral trait: using light, petSafe, room or size silently narrows results to plants with an indoor profile, plus the fact that results are short profiles with links rather than full records. Pagination behavior is left to the schema.

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?

Two sentences, front-loaded with the core search-and-filter scope before the indoor caveat and the get_plant handoff. The first sentence is dense with a long filter list, but each clause carries distinct information and nothing is redundant filler.

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 20-parameter, zero-required, no-output-schema tool, the description covers scope, the indoor-filter coupling, the return shape (short profiles with links) and the next step. It does not mention paging beyond the schema's offset/limit docs, and does not say what it will not find, leaving minor gaps.

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?

Schema description coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by mapping intent phrasing onto specific parameters ("by name (English, botanical or Arabic), category, sun, water need, minimum tolerance ratings, use, garden style or planting month") and by tying the indoor-scenario example to the four indoor filters, which helps an agent translate a user question into the right filter set.

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?

States a specific verb and resource (search/filter the Dubai-rated plant library) and enumerates the filter surface. It also names the sibling it is not ("call get_plant for the full one"), so an agent can separate the short-profile search from the detail-fetch tool without opening schemas.

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?

Gives concrete usage contexts, including a worked natural-language case ("low light, pet friendly plants for a Dubai apartment") and the handoff to get_plant for full profiles. It does not disambiguate against other search-adjacent siblings such as what_to_plant or get_indoor_plant_guide, so the routing guidance is clear but not exhaustive.

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 tools Inspect

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

Need Help?