Realty In Au MCP Server

propertiesv3lookup

Find off-market Australian properties by ID to access detailed property history and information through Realty In Au MCP Server.

Instructions

Look for off-market property by id

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": {
      "id": "<id>"
    },
    "name": "propertiesv3lookup"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The value of 'id' field returned in .../auto-complete endpoint with display as 'Property history'	6041048

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'off-market property', hinting at data scope, but lacks critical behavioral details: whether this is a read-only lookup, requires authentication, has rate limits, returns structured data or errors, or what 'look for' entails (e.g., search vs. fetch). The description is minimal and misses key operational context.

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?

Extremely concise with a single, front-loaded sentence: 'Look for off-market property by id'. Every word earns its place, with no redundancy or fluff. The structure is clear and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a simple parameter (1 param with 100% coverage), the description is incomplete. It lacks details on behavior, return values, error handling, and differentiation from siblings. For a lookup tool, users need to know what data is returned and any constraints, which are missing here.

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 description coverage is 100%, with the parameter 'id' fully documented in the schema (type, default, description). The description adds no additional meaning beyond stating it's used 'by id', which the schema already covers. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Look for') and resource ('off-market property'), specifying it's by 'id'. It distinguishes from siblings like 'propertieslist' (list all) and 'propertiesdetail' (likely general details), but doesn't explicitly contrast with deprecated 'propertieslookup_deprecated' or 'propertiesv2lookup_deprecated'. The purpose is specific but sibling differentiation is implicit.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. It implies usage for off-market properties by ID, but doesn't state when to choose it over 'propertiesdetail' (which might handle on-market) or the deprecated lookup tools. No prerequisites, exclusions, or named alternatives are provided.

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

Deploy Server