Garden Design MCP Server

get_objects_in_zone

Retrieves all garden objects whose center lies within a specified zone, including plants, buildings, and ground shapes. Use it to check plant density, verify placement, or list zone contents.

Instructions

Returns all garden objects whose center falls within the specified zone. Includes plants, buildings, and ground shapes. Useful for checking plant density, verifying placement, or listing zone contents.

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": {
      "zoneId": "<zoneId>"
    },
    "name": "get_objects_in_zone"
  }
}

Input Schema

Name	Required	Description	Default
`zoneId`	Yes	ID of the zone to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.9.3Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral rule — containment is determined by object center, not bounding-box overlap — and enumerates the object types covered. It omits return ordering, behavior for an unknown/empty zone, and result size, which matter for a query tool with no output schema.

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 short sentences with zero filler: the effect and containment rule come first, then the returned content, then use cases. Every sentence adds information.

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 one-parameter read tool with no annotations and no output schema, the definition covers what is returned conceptually and how containment is judged, which is enough to invoke it correctly. The remaining gap is the shape/count of the response, which an agent may still want before planning downstream work.

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% for the single zoneId parameter, so the schema already documents that it is the zone to query. The description reinforces this by tying the result set to that zone's boundary, but adds no syntax, format, or lookup details beyond the schema.

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 gives a specific verb and resource (returns garden objects) plus a precise spatial scope: objects whose CENTER falls within the zone, which clarifies that straddling objects are excluded. It also names the object categories returned (plants, buildings, ground shapes). It stops short of explicitly distinguishing itself from the sibling get_objects, which returns objects without a zone filter.

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?

It offers use cases (checking plant density, verifying placement, listing zone contents), which implies when the tool is appropriate. However, it never states when NOT to use it or names alternatives such as get_objects for cross-zone queries or get_zones/get_zone_analysis for zone metadata, so the agent must infer the routing itself.

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

Deploy Server