mbs_profileThe mesh block's upward ABS chain — SA1, SA2/3/4, GCCSA, state — plus the parallel admin chain (LGA, suburb (SAL), postcode).
Price: 3¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| mb_code | 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": "Upward ABS chain for a mesh block, plus admin attributes.",
- "example": {
- "gccsa": "Rest of NSW",
- "lga": "Lake Macquarie",
- "mesh_block": "10434270000",
- "postcode": "2280",
- "sa1": "11101120618",
- "sa2": "Belmont - Bennetts Green",
- "sa3": "Lake Macquarie - East",
- "sa4": "Newcastle and Lake Macquarie",
- "state": "NSW",
- "suburb": "Belmont North"
- },
- "properties": {
- "gccsa": {
- "description": "Greater Capital City Statistical Area.",
- "title": "Gccsa",
- "type": "string"
- },
- "lga": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Local Government Area.",
- "title": "Lga"
- },
- "mesh_block": {
- "description": "ABS Mesh Block code.",
- "title": "Mesh Block",
- "type": "string"
- },
- "postcode": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Postcode (POA).",
- "title": "Postcode"
- },
- "sa1": {
- "description": "SA1 code.",
- "title": "Sa1",
- "type": "string"
- },
- "sa2": {
- "description": "SA2 name.",
- "title": "Sa2",
- "type": "string"
- },
- "sa3": {
- "description": "SA3 name.",
- "title": "Sa3",
- "type": "string"
- },
- "sa4": {
- "description": "SA4 name.",
- "title": "Sa4",
- "type": "string"
- },
- "state": {
- "description": "State / Territory.",
- "title": "State",
- "type": "string"
- },
- "suburb": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Suburb (SAL).",
- "title": "Suburb"
- }
- },
- "required": [
- "mesh_block",
- "sa1",
- "sa2",
- "sa3",
- "sa4",
- "gccsa",
- "state"
- ],
- "title": "MeshBlockProfile",
- "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[MeshBlockProfile]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_MeshBlockProfile_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the cost per call (3¢) which is useful, but it does not describe any other behavioral aspects such as rate limits, authentication, or error handling. Since annotations cover the main behavioral traits, a 3 is appropriate.
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, consisting of two lines, and front-loads the main content. The inclusion of pricing is efficient and useful. No wasted words.
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?
The description covers the main purpose and output structure (the chains), but lacks details on parameter format, return format (codes vs names), and error behavior. Given the tool's simplicity and annotation coverage, it's adequate but not fully complete.
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 only defines mb_code as a string with no description, and the description does not explain the expected format or content of mb_code (e.g., whether it's a numeric code, length, or example). With 0% schema coverage, the description fails to compensate, leaving the agent without guidance on how to construct a valid parameter.
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 explicitly states that the tool returns the mesh block's upward ABS chain (SA1, SA2/3/4, GCCSA, state) and the parallel admin chain (LGA, suburb, postcode). This is specific about the resource (mesh block) and the output, distinguishing it from sibling profile tools like lga_profile or sa4_profile which target different geographic levels.
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?
The description implies usage when a mesh block code is known and the parent geographic chains are needed, but it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or prerequisites. Given the clear subject, it's inferred but not explicit.
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.