SPACEXPLORATION

Search listings

search_listings

Read-only

Search commercial real estate listings. Returns paginated hits with facet counts; every hit carries the public url to cite and its listed_at / updated_at stamps. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters — and its bounds, when present — here.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-based). Defaults to 1.
`sort`	No	Sort key. Valid values from get_registry sort_options (e.g. "listed_at:desc", "price:asc").
`query`	No	Free-text search query (street address, city, or keyword). Omit or pass null for no text filter.
`bounds`	No	Geographic bounding box (degrees) limiting hits to an area. Forward the bounds returned by interpret_search verbatim to honour "near <place>" intent; omit for a nationwide search.
`filters`	No	Structured filter map keyed by Typesense field name. Ranges as {min?, max?}, multi-select as string[], booleans as true/false. Call get_registry to see valid field names and allowed values.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 11, 2026

addedInput schema / properties / bounds

Added value: +{
+  "description": "Geographic bounding box (degrees) limiting hits to an area. Forward the bounds returned by interpret_search verbatim to honour \"near <place>\" intent; omit for a nationwide search.",
+  "properties": {
+    "ne_lat": {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    "ne_lng": {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    },
+    "sw_lat": {
+      "maximum": 90,
+      "minimum": -90,
+      "type": "number"
+    },
+    "sw_lng": {
+      "maximum": 180,
+      "minimum": -180,
+      "type": "number"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedJun 9, 2026

TDQS

A4.5/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), so the description's added value is the return contract: paginated hits, facet counts, a public url for citation, and listed_at/updated_at stamps. With no output schema, this disclosure is genuinely useful, though pagination limits and rate behavior remain unspecified.

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?

Three sentences, each earning its place: purpose, return contract, then the recommended workflow. Purpose is front-loaded 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 5-param, zero-required, fully schema-documented read tool with no output schema, the description supplies the missing pieces: what comes back (hits, facets, citable url, timestamps) and how to sequence it with interpret_search. An agent has everything needed to call it correctly.

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%, so page, sort, query, bounds, and filters are already documented in the schema. The description reiterates the bounds-forwarding rule that the schema itself already states ('Forward the bounds returned by interpret_search verbatim'), so it adds little beyond the baseline.

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 and resource ('Search commercial real estate listings') and distinguishes itself from siblings like get_listing and list_my_listings by scope. It also specifies the return shape (paginated hits with facet counts) up front.

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?

Gives an explicit workflow rule: for AI-driven search, call interpret_search first to convert natural language into structured filters, then pass those filters and bounds here. This names the prerequisite sibling tool and the condition that triggers it.

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

All SPACEXPLORATION 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?