Microburbs Australian Property Data

Search endpoints

search_endpoints

Read-onlyIdempotent

Find which Microburbs tool answers a question, in plain words — e.g. "how many people rent in Bondi", "is this house in a flood zone", "schools near 10 Smith St". Typo-tolerant, knows synonyms. Returns the best tools first, each with its MCP tool name, REST path, price in cents and a description. Free.

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": {
      "query": "<query>"
    },
    "name": "search_endpoints"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by disclosing typo tolerance, synonym awareness, ranked results, and that the call is free. Listing fields inside each result is slightly redundant with the output schema, but the ranking and fuzzy-matching behavior is value that annotations cannot convey.

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?

Four compact clauses, front-loaded with the purpose, examples embedded inline, zero filler. Every phrase adds either scope, tolerance behavior, or result shape.

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?

With an output schema present, the description rightly does not dwell on return values, and it hints at their content anyway. For a simple two-parameter discovery tool this is nearly complete; only `limit` guidance and empty-result behavior are missing.

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 0% for two parameters. The description compensates well for `query` by illustrating natural-language phrasing, but `limit` (default 5) is never mentioned, so half the parameters remain undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ("Find which Microburbs tool answers a question") and immediately grounds it in three plain-language example questions. The meta/discovery role is unmistakable and cannot be confused with the concrete data tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples of the kinds of questions to route here ("how many people rent in Bondi", "is this house in a flood zone") give a clear picture of when to reach for this tool. It stops short of explicit exclusions or naming an alternative to use instead when the question is already known to map to a specific tool.

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

All Microburbs Australian Property Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?