properties_schools_allSchools for this address: the ones nearby with their distances, and how each ranks on NAPLAN alongside sector, level and attendance.
The priciest bundle in the Property family, because it joins the school
register, the ranking table and distance calculations. Call
/schools/nearby alone if rankings do not matter.
Price: 105¢ 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": [
- {
- "description": "All nearby schools — list + ranking.",
- "example": {
- "nearby": [
- {
- "distance_m": 612,
- "name": "Belmont North Public School",
- "school_level_type": "Primary",
- "sector": "public"
- }
- ],
- "ranking": [
- {
- "attendance_rate": 0.89,
- "distance_m": 612,
- "name": "Belmont North Public School",
- "naplan_label": "Top 40%",
- "naplan_rank": 0.63,
- "school_level_type": "Primary",
- "sector": "public",
- "socioeconomic_label": "Bottom 20%",
- "socioeconomic_rank": 0.17
- }
- ]
- },
- "properties": {
- "nearby": {
- "anyOf": [
- {
- "items": {
- "additionalProperties": true,
- "description": "One school within ~5km of the property.",
- "example": {
- "distance_m": 612,
- "id": 42002,
- "name": "Belmont North Public School",
- "school_level_type": "Primary",
- "sector": "public"
- },
- "properties": {
- "distance_m": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Distance from the property in metres.",
- "title": "Distance M"
- },
- "id": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "School identifier (MySchool ID).",
- "title": "Id"
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "School name.",
- "title": "Name"
- },
- "school_level_type": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Primary / Secondary / Combined.",
- "title": "School Level Type"
- },
- "sector": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "public / private.",
- "title": "Sector"
- }
- },
- "title": "SchoolNearby",
- "type": "object"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "title": "Nearby"
- },
- "ranking": {
- "anyOf": [
- {
- "items": {
- "additionalProperties": true,
- "description": "One school within ~5km, ranked by NAPLAN + socio-economic percentiles.",
- "example": {
- "attendance_rate": 0.89,
- "distance_m": 612,
- "id": 42002,
- "name": "Belmont North Public School",
- "naplan_label": "Top 40%",
- "naplan_rank": 0.63,
- "school_level_type": "Primary",
- "sector": "public",
- "socioeconomic_label": "Bottom 20%",
- "socioeconomic_rank": 0.17
- },
- "properties": {
- "attendance_rate": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Mean attendance rate (0–1).",
- "title": "Attendance Rate"
- },
- "distance_m": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Distance from the property in metres.",
- "title": "Distance M"
- },
- "id": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "School identifier (MySchool ID).",
- "title": "Id"
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "School name.",
- "title": "Name"
- },
- "naplan_label": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable NAPLAN band — 'Top 5%', 'Top 40%', etc.",
- "title": "Naplan Label"
- },
- "naplan_rank": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "NAPLAN rank percentile (0–1, higher = better).",
- "title": "Naplan Rank"
- },
- "school_level_type": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Primary / Secondary / Combined.",
- "title": "School Level Type"
- },
- "sector": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "public / private.",
- "title": "Sector"
- },
- "socioeconomic_label": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable affluence band.",
- "title": "Socioeconomic Label"
- },
- "socioeconomic_rank": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Socio-economic rank percentile (0–1, higher = more advantaged).",
- "title": "Socioeconomic Rank"
- }
- },
- "title": "SchoolRanking",
- "type": "object"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "title": "Ranking"
- }
- },
- "title": "SchoolsAll",
- "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[SchoolsAll]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SchoolsAll_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false, destructiveHint=false), so the bar is lower. The description adds genuinely behavioral context beyond them: this is the priciest bundle at 105¢ per call, and why (it joins three underlying datasets), which matters for a cost-sensitive agent choosing among siblings.
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?
Front-loaded with purpose, then cost rationale and the alternative in descending priority. Uses markdown bold for the price line, which is a minor stylistic noise but does flag the most decision-relevant fact; every sentence earns its place.
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?
No output schema exists, and the description compensates by naming the facets returned (distances, NAPLAN ranking, sector, level, attendance). Combined with annotations covering safety and idempotency and a stated cost, the only omission is the gnaf_id input contract, so an agent has almost everything needed to call it.
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% for the single required `gnaf_id`, so the description must carry the parameter's meaning. It only implies the input is 'this address' and never explains what a GNAF ID is or how to obtain one, leaving a real gap for a tool that is otherwise well specified.
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?
States a specific verb and resource (schools for an address), enumerates the returned facets (nearby distances, NAPLAN ranking, sector, level, attendance), and distinguishes itself from the unbundled sibling by noting it joins the register, ranking table and distance calculations. An agent can separate this bundle from properties_schools_nearby and properties_schools_ranking without opening a schema.
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?
Explicitly routes the agent: use this bundle unless rankings do not matter, in which case call `/schools/nearby` alone. That is a clear when/when-not condition anchored to a cost tradeoff. The alternative is referenced by path-style name (`/schools/nearby`) rather than the exact sibling tool name, which slightly weakens the routing.
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.