properties_surroundings_parcelsCadastral parcel polygons (GeoJSON) for properties around the subject.
Price: 25¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| gnaf_id | Yes |
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": "Cadastral parcel polygons for every property around the subject.",
- "example": {
- "count": 127,
- "gnaf_pid": "GANSW704360755",
- "parcels": {
- "features": [
- {
- "geometry": {
- "coordinates": [
- [
- [
- [
- 151.221417,
- -33.800987
- ],
- [
- 151.221318,
- -33.801078
- ],
- [
- 151.221308,
- -33.801256
- ],
- [
- 151.221417,
- -33.800987
- ]
- ]
- ]
- ],
- "type": "MultiPolygon"
- },
- "properties": {
- "gnaf_pid": "GANSW704355807",
- "is_subject": false
- },
- "type": "Feature"
- }
- ],
- "type": "FeatureCollection"
- },
- "radius_m": 200
- },
- "properties": {
- "count": {
- "description": "Number of parcel features returned.",
- "title": "Count",
- "type": "integer"
- },
- "gnaf_pid": {
- "description": "The subject property's GNAF PID.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "parcels": {
- "additionalProperties": true,
- "description": "GeoJSON FeatureCollection, one feature per parcel.",
- "properties": {
- "features": {
- "description": "One feature per parcel.",
- "items": {
- "additionalProperties": true,
- "description": "One cadastral parcel as a GeoJSON Feature.",
- "properties": {
- "geometry": {
- "additionalProperties": true,
- "description": "Parcel polygon, 6 dp coords.",
- "properties": {
- "coordinates": {
- "description": "Nested coordinate arrays per the GeoJSON spec, lon first.",
- "title": "Coordinates"
- },
- "type": {
- "description": "GeoJSON geometry type, e.g. 'MultiPolygon'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "coordinates"
- ],
- "title": "GeoJsonGeometry",
- "type": "object"
- },
- "properties": {
- "additionalProperties": true,
- "description": "Feature properties: `gnaf_pid` and `is_subject`.",
- "title": "Properties",
- "type": "object"
- },
- "type": {
- "const": "Feature",
- "description": "Always 'Feature'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "properties",
- "geometry"
- ],
- "title": "ParcelFeature",
- "type": "object"
- },
- "title": "Features",
- "type": "array"
- },
- "type": {
- "const": "FeatureCollection",
- "description": "Always 'FeatureCollection'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "features"
- ],
- "title": "ParcelFeatureCollection",
- "type": "object"
- },
- "radius_m": {
- "description": "Radius of the search box around the subject, metres.",
- "title": "Radius M",
- "type": "integer"
- }
- },
- "required": [
- "gnaf_pid",
- "radius_m",
- "count",
- "parcels"
- ],
- "title": "SurroundingParcels",
- "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[SurroundingParcels]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SurroundingParcels_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by specifying the output format (GeoJSON) and the cost (25¢ per call), which are not in the annotations. However, it does not disclose behavior such as error handling, empty results, or the exact meaning of 'around the subject' beyond the title's 200 m radius.
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 extremely concise, with two short sentences. The primary purpose is front-loaded ('Cadastral parcel polygons...'), and the cost is secondary. There is no filler or redundancy, making it highly efficient.
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 tool with one parameter and no output schema, the description is incomplete. It fails to explain the gnaf_id parameter, which is critical given zero schema coverage. It also omits the 200 m radius (though present in the title) and any information about error responses or empty results. The tool is simple, but the missing parameter documentation leaves an agent uncertain about how to construct a valid call.
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?
Schema description coverage is 0%, so the description must compensate for the single required parameter gnaf_id. It does not explain what gnaf_id is (e.g., a G-NAF identifier) or how it should be formatted. The only hint is the phrase 'for properties around the subject,' which implies gnaf_id identifies the subject property, but this is not explicit. The description adds minimal meaning beyond the schema.
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 states the tool returns 'Cadastral parcel polygons (GeoJSON) for properties around the subject.' This is a specific resource (cadastral parcels) and output format (GeoJSON), distinguishing it from siblings like properties_surroundings_properties or properties_surroundings_tenure. The title adds the 200 m radius, further clarifying scope.
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?
There is no explicit guidance on when to use this tool versus alternatives. The description does not mention any exclusions, alternatives, or conditions (e.g., 'use this when you need parcel boundaries' or 'for property details use properties_surroundings_properties'). Usage must be inferred from the name and description, but no direct comparison is provided.
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.