MCP Tool Routing

Conduit proxies standard MCP JSON-RPC methods to the upstream MLS data feed. Responses pass through the governance pipeline, which applies field-level access control based on the MLS's policy.

Supported JSON-RPC methods

tools/list

Discover available tools on the MLS data feed.

json

{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "id": 1
}

tools/call

Execute a tool with arguments. This is the primary method for querying property data.

json

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "search_properties",
    "arguments": {
      "city": "Austin",
      "propertyType": "Residential",
      "minPrice": 300000,
      "maxPrice": 500000
    }
  },
  "id": 2
}

resources/read

Read a specific resource by URI (e.g., a single listing by ID).

json

{
  "jsonrpc": "2.0",
  "method": "resources/read",
  "params": {
    "uri": "listing://MLS-2024-12345"
  },
  "id": 3
}

Governed responses

When you query through the gateway, responses are filtered according to the MLS's governance policy. Fields may be visible, masked, or hidden entirely.

Visible

Field passes through unchanged. Most address, property, and listing fields are visible by default.

Masked

Field value is replaced with a mask pattern. Example: ListAgentEmail → "***@***.com"

Hidden

Field is removed entirely from the response. You will not see the key at all. Example: ListAgentDirectPhone is omitted.

RESO field structure

Conduit recognizes 60 RESO Data Dictionary fields across 7 categories. MLS policies control access at the individual field level.

Category	Fields	Examples
address	8	StreetAddress, City, PostalCode
property	10	PropertyType, BedroomsTotal, LivingArea, YearBuilt
listing	12	ListingId, StandardStatus, ListPrice, DaysOnMarket
agent	12	ListAgentFullName, ListOfficeName, BuyerAgentEmail
financial	8	TaxAnnualAmount, TaxAssessedValue, AssociationFee
media	5	Media, PhotosCount, MainImageURL
compliance	5	CopyrightNotice, DisclaimerText, DataSource

[i]Field sensitivity levels

Each field has a base sensitivity: public, restricted, or private. MLS policies can override these defaults. For example, an MLS might hide a public field or make a restricted field visible to trusted vendors.

Result limits

MLS policies enforce a maximum number of results per query. Arrays of listing objects are truncated to the policy limit:

Policy	Max results/query
Standard Access	50
Restricted Access	25
Open Data	100

Next: Response Format →

←Gateway Routing Response Format→