Skip to main content
Use the Trestle MCP server to answer listing questions in an agent without hand-writing API calls — for example, finding active homes that match a client’s criteria, sizing local inventory, or checking an address against MLS data. All six tools are read-only.

Data scope


trestle-search_property

Searches Trestle Property records using OData query arguments. When to use:
  • You need listings that match price, status, location, or feature criteria
  • You need specific fields for a known listing
  • You need listings with open houses, using expand_expression
Examples:
  • “Find active homes in Austin listed between $400,000 and $600,000”
  • “Show the five most recently reduced listings in Denver”

Input schema

Example request

Output schema

An OData collection. Rows are in value, and the total match count is in @odata.count when you set count_required. Null fields are omitted, and zero values are kept.

trestle-aggregate_property

Counts Property records grouped by one to three scalar fields. Results are exact and bounded. When to use:
  • You need counts by status, property type, city, or another scalar field
  • You need a market snapshot without downloading every row
Examples:
  • “How many active listings are there in Austin by property type?”
  • “Count listings by status in Seattle”

Input schema

Example request

Output schema

One entry per group, with the grouped field values and a count. If more records match than max_records, the tool returns a limit_exceeded problem and no partial groups.

trestle-lookup_enumerations

Looks up the valid values for a Trestle lookup field. When to use:
  • You need the exact literal for a status, property type, or feature field before filtering
  • You need to list every value a lookup accepts
Examples:
  • “What are the valid listing statuses?”
  • “What pool features can I filter on?”

Input schema

Example request


trestle-search_entity

Searches a supported Trestle entity set other than Property, such as Member, Office, OpenHouse, or Field. When to use:
  • You need open house schedules, agents, offices, or field metadata
  • You need to discover which fields exist on a resource
Examples:
  • “List the fields available on the Property resource”
  • “Which open houses are scheduled this weekend?”

Input schema

For open houses filtered by city or status, use trestle-search_property with expand_expression="OpenHouse(...)". Schedule fields live on OpenHouse, but address, city, price, and status live on the related Property.

Example request


trestle-get_property_information

Returns compact property information for one or more street addresses. When to use:
  • You have addresses and want listing data without writing an OData filter
  • You need to check several addresses in one call
Examples:
  • “Get the listing details for 123 Main St, Austin, TX 78701”
  • “Look up these three addresses and tell me which are active”

Input schema

Example request


trestle-lint_trestle_odata_query

Checks OData query arguments without running them. It is advisory: passing lint doesn’t guarantee the query succeeds, and warnings flag behavior the linter couldn’t verify. When to use:
  • Before any nontrivial search_property, search_entity, or aggregate_property call
  • When the query uses unfamiliar fields, enum literals, null checks, $apply, or paging
  • When a query failed and you need to know why
Examples:
  • “Check whether this filter is valid before I run it”

Input schema

Takes the same arguments as trestle-search_entity: entity_set (required) plus the OData expression arguments (filter_expression, select_expression, orderby_expression, top_count, skip_count, count_required, expand_expression, search_expression, and apply_expression).

Example request

Output schema

A lint result with a verdict of pass or fail and a list of issues. Each issue carries a rule_id. The example above fails with a field-to-field comparison rule, because Trestle can’t compare two fields in a filter. Compare them client-side instead.

Errors and limits

Failures return an RFC 9457 Problem Details object with isError: true. A failing lint preflight returns a 422 validation-error with preflight: true, and the request never reaches Trestle.