constellation1-mcp-server

reso_query

Query the RESO API for real estate data: property listings, agent info, office details, and market analytics. Supports filtering, sorting, and pagination for MLS research and lead generation.

Instructions

Query the RESO (Real Estate Standards Organization) API for comprehensive real estate data. This tool provides access to MLS (Multiple Listing Service) data including property listings, agent information, office details, media files, and market analytics. Perfect for real estate research, market analysis, property searches, and lead generation. Supports advanced filtering, sorting, and field selection with standardized RESO field names for consistent data access across different MLS systems.

Input Schema

TableJSON Schema

Name	Required	Description
`top`	No	Maximum number of records to return (1-1000). Use 10-50 for quick searches, 100-1000 for analysis.
`skip`	No	Number of records to skip for pagination. Skip limits: Property (1M), Office/Member (500K), Media (50K)
`entity`	No	RESO Entity to query. Options: Property (listings), Member (agents), Office (brokerages), Media (photos/videos), OpenHouse (events), Dom (days on market), PropertyRooms (room details), PropertyUnitTypes (unit info), RawMlsProperty (raw MLS data)
`expand`	No	Include related entities. Examples: "Media", "Media($filter=Permission ne 'Private')", "Media,OpenHouse,Dom"
`filter`	No	OData filter expression. Examples: "StandardStatus eq 'Active'", "ListPrice ge 200000 and ListPrice le 500000", "City eq 'Seattle'"
`select`	No	Comma-separated list of fields to return. Leave empty to get all available fields. Common Property fields: ListingKey, StandardStatus, ListPrice, BedroomsTotal, City, PublicRemarks
`orderby`	No	Sort order. Format: "FieldName [asc\|desc]". Examples: "ListPrice desc", "City asc, ModificationTimestamp desc"
`nextLink`	No	Use @odata.nextLink URL from a previous query response to get the next page of results. When provided, other parameters (except ignorenulls/ignorecase) are ignored. This enables efficient server-side pagination for large result sets. Example: use the @odata.nextLink value from a previous reso_query response.
`ignorecase`	No	Enable case-insensitive text matching for filters. Default: false.
`ignorenulls`	No	Exclude null/empty fields to reduce payload size. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-devSep 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only says 'Query' and 'data access.' It does not explicitly state the operation is read-only, mention authentication/rate-limit implications, or clarify how nextLink/pagination behaves, which is important for a 10-parameter API tool.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but contains filler phrases like 'Perfect for' and 'comprehensive' and repeats the MLS/RESO concept across multiple sentences. It is acceptable but not tightly edited.

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

Completeness3/5

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

The rich input schema covers parameters, but there is no output schema and the description does not describe response shape, pagination behavior, or how results are returned. It identifies data categories and use cases, making it minimally adequate for a query tool.

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 the schema already documents every parameter. The description adds high-level color about filtering, sorting, and field selection, but does not provide significant meaning beyond the schema, meriting the baseline score.

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 identifies the action ('Query the RESO API') and the resource domain (MLS property, agent, office, media, and analytics data), making the tool's purpose easy to grasp. It does not explicitly distinguish itself from the sibling reso_help, so it stops short of a 5.

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?

It offers broad intended-use context ('Perfect for real estate research, market analysis, property searches, and lead generation') but no explicit conditions for when to use this tool instead of reso_help, nor any exclusions. The guidance is implied rather than prescriptive.

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

Deploy Server

reso_query

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools