properties_amenities_nearbyCurated amenities (supermarkets, green spaces, restaurants/cafes)
within radius_m of the property, bucketed and nearest-first.
Price: 10¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| gnaf_id | Yes | ||
| radius_m | No | Search radius in metres (100–5000, default 1000). |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "properties": {
- "available": {
- "anyOf": [
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
- ],
- "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
- "title": "Available"
- },
- "data": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Curated amenities within the radius, bucketed and nearest-first.",
- "example": {
- "center_lat": -33.802479,
- "center_lng": 151.219715,
- "counts": {
- "green_spaces": 4,
- "restaurant": 11,
- "supermarket": 2
- },
- "gnaf_id": "GANSW704360755",
- "radius_m": 1000,
- "results": [
- {
- "category": "Supermarket",
- "distance_m": 240,
- "lat": -33.8011,
- "lng": 151.2216,
- "name": "Castlecrag Village"
- },
- {
- "category": "Green Spaces",
- "distance_m": 190,
- "lat": -33.8038,
- "lng": 151.218
- }
- ]
- },
- "properties": {
- "center_lat": {
- "description": "Property latitude (WGS84).",
- "title": "Center Lat",
- "type": "number"
- },
- "center_lng": {
- "description": "Property longitude (WGS84).",
- "title": "Center Lng",
- "type": "number"
- },
- "counts": {
- "additionalProperties": {
- "type": "integer"
- },
- "description": "Count per bucket within the radius (exact, pre-cap).",
- "title": "Counts",
- "type": "object"
- },
- "gnaf_id": {
- "description": "GNAF property identifier.",
- "title": "Gnaf Id",
- "type": "string"
- },
- "radius_m": {
- "description": "Search radius applied, metres.",
- "title": "Radius M",
- "type": "integer"
- },
- "results": {
- "description": "Amenities, nearest first (capped at 80).",
- "items": {
- "additionalProperties": true,
- "description": "One nearby amenity.",
- "properties": {
- "category": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Bucket: Supermarket / Green Spaces / Restaurant.",
- "title": "Category"
- },
- "distance_m": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Straight-line distance from the property, metres.",
- "title": "Distance M"
- },
- "lat": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Latitude (WGS84).",
- "title": "Lat"
- },
- "lng": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Longitude (WGS84).",
- "title": "Lng"
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Amenity name, where known.",
- "title": "Name"
- }
- },
- "title": "AmenityRow",
- "type": "object"
- },
- "title": "Results",
- "type": "array"
- }
- },
- "required": [
- "gnaf_id",
- "center_lat",
- "center_lng",
- "radius_m",
- "counts",
- "results"
- ],
- "title": "AmenitiesNearby",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "The endpoint's payload, or `null` when Microburbs has no value."
- },
- "message": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable explanation. Omitted on success.",
- "title": "Message"
- },
- "reason": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
- "title": "Reason"
- }
- },
- "title": "ApiResponse[AmenitiesNearby]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_AmenitiesNearby_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful extras: results are bucketed and nearest-first, and each call costs 10¢. That pricing disclosure is materially relevant to invocation decisions. Rate limits/auth are not mentioned, but the annotation safety profile lowers the burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two tight sentences: the first front-loads the output categories, radius, and ordering; the second states the price. There is no filler, and the backtick parameter reference is precise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read-only lookup, this covers the output categories, radius, ordering behavior, and cost, with safety covered by annotations. It does not describe the exact return shape or clarify that gnaf_id identifies the property, so it is slightly incomplete for an agent without prior context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents radius_m fully, and the description merely reuses it as a radius filter rather than adding parameter detail. The required gnaf_id has no schema description and the description does not explain it either, so at 50% schema coverage the definition under-serves parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly names the resource—curated nearby amenities for a property—and specifies the categories and radius behavior, so an agent can tell it is an amenity lookup. It lacks an explicit verb such as 'Returns' and does not name any sibling, though the category list implicitly separates it from transport/schools nearby tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is implied: an agent should call this when it needs supermarkets, green spaces, or restaurants/cafes around a property. There is no explicit when-to-use/when-not-to-use guidance or alternative routing, which matters given nearby sibling tools like properties_transport_nearby and properties_schools_nearby.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.