Homejourney Singapore property listings

Find Homejourney listings to cite

search

Read-only

Search active Homejourney Singapore property listings for deep-research and citation hosts. Broad availability questions are supported; use location, project, or feature keywords only when the user supplied them. Returns canonical listing URLs for citations. When no listing matches, returns the Homejourney guides that answer the question (IDs starting guide:), or an empty list with a note naming the next tool. To filter by price, bedrooms, area or rent terms, use search_listings instead.

Input Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

Name	Required	Description	Default
`note`	No	Set only when results is empty: why, and which tool to call next.
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Set only when results is empty: why, and which tool to call next.",
+  "type": "string"
+}

First observedOct 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral context beyond them: canonical URLs are returned, and there is a disclosed fallback path returning guide: prefixed IDs or an empty list with a note naming the next tool. It does not discuss result volume or pagination, so it falls short of the top mark.

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 sentences, each doing distinct work: purpose, query construction, return value, fallback. The alternative-tool routing is placed last, after the core behavior, and there is no filler.

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

Completeness5/5

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

For a one-parameter search tool, the description covers selection, query phrasing, return semantics, and the no-match fallback, and an output schema exists so return-value details need no elaboration. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter is a bare string, so the description carries the burden — and it does add meaning by prescribing broad availability phrasing and limiting location/project/feature keywords to user-supplied ones. It stops short of stating query syntax or matching behavior, so not a 5.

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 specific verb (search) and resource (active Homejourney Singapore property listings) with a stated consumer (deep-research and citation hosts). It also distinguishes itself from the nearest sibling, search_listings, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicitly declares the supported query style ('Broad availability questions are supported'), constrains keyword use to user-supplied terms, and names the alternative tool (search_listings) with the exact conditions that select it (price, bedrooms, area, rent terms).

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

All Homejourney Singapore property listings 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?