Microburbs Australian Property Data

Datasets · Describe a dataset

datasets_describe

Read-onlyIdempotent

What a dataset is, what it shows, why you would use it and how it is built; its fields and units, coverage, refresh cycle and an example call.

Price: 1¢ per call.

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": {
      "slug": "<slug>"
    },
    "name": "datasets_describe"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Dataset slug from /v1/datasets.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by stating the price of 1¢ per call and by enumerating the returned content in the absence of an output schema. It says nothing about response size, errors on unknown slugs, or caching.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence lists the returned material, followed by a short standalone price note that is easy to spot. The opening clause is slightly padded ('what it is, what it shows, why you would use it') but nothing is redundant enough to cut.

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?

For a cheap, read-only, single-parameter lookup with no output schema, the description covers both the informational payload and the per-call cost, which is what an agent needs to decide whether to call it. Missing only edge-case behavior such as invalid-slug handling or response size.

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?

Only one parameter exists and the schema documents it at 100% coverage, including the source path /v1/datasets and an example value. The description adds no meaning about slug format, case sensitivity, or behavior on an invalid slug, so the baseline 3 applies.

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

Purpose4/5

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

The description enumerates exactly what the call returns: definition, purpose, build method, fields and units, coverage, refresh cycle, and an example call. That is a specific, content-level statement of purpose for a describe-by-slug tool. It stops short of naming the sibling `datasets` list as the source of slugs, so differentiation rests on the schema rather than the prose.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this to learn a dataset's fields before querying it. There is no explicit 'use this when' or 'use X instead' guidance, and no mention of where slugs come from within the description itself (that lives only in the schema).

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?