Skip to main content
Glama
dragosh29

Dezrez Rezi MCP server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search properties

search_properties
Read-onlyIdempotent

Search property marketing roles by address or postcode with filters for on-market, role type, and role status. Returns property ID, address, prices, and owning group.

Instructions

Search the agency's property marketing roles (a property being sold or let) by free text such as an address fragment or postcode, optionally only those on the market, of one role type (documented examples: Sales, Letting) or in one role status (documented examples: OfferAccepted, Exchanged). Each result carries the property ID, address, the role with its status, prices, a summary line and the owning group. Uses GET /api/role/suggest; the role type and status values are system names the swagger does not enumerate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoAPI page number to start from (1-based, as this server assumes; use next_page from a previous call)
queryNoFree-text search (API parameter `dataContract.query`)
role_typeNoRole type system name, e.g. Sales or Letting (`dataContract.roleType`)
max_resultsNoMost records to return in this call; whole API pages only, so fewer may come back with a next_page to continue from
role_statusNoRole status system name, e.g. OfferAccepted (`dataContract.roleStatus`)
is_on_marketNoOnly roles currently on the market (`dataContract.isOnMarket`)
suggest_typeNoThe two values the spec documents for `dataContract.suggestType`
include_contact_detailsNoInclude the owning group's members' email addresses, phone numbers and postal addresses, and stop redacting emails and phone numbers from names and summary text. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: the backing endpoint, the result shape, the redaction behavior of include_contact_details, and the caveat that role type/status values are system names not enumerated in swagger.

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?

The description is appropriately sized and front-loaded: it begins with the core search behavior, then describes results and implementation caveats. Every sentence adds useful information without repetition.

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?

Given eight optional parameters, no output schema, and rich annotations, the description is complete enough. It explains the searchable filters, the return fields, the pagination-related schema context, and the important enumeration caveat for role type/status.

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 description coverage is 100%, so baseline is 3. The description adds meaningful parameter semantics by giving examples for role_type and role_status and warning that their system names are not enumerated by swagger, which goes beyond the schema text.

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?

States a specific verb and resource: searching the agency's property marketing roles by free text, with optional filters. The role-oriented scope clearly separates it from property-entity siblings like get_property, but it does not explicitly name or contrast those alternatives.

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?

Provides clear usage context, such as searching by address fragment or postcode and optionally filtering by on-market status, role type, or role status. However, it does not explicitly state when to use this instead of get_property or other sibling tools, leaving routing guidance implied.

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

Deploy Server

Other Tools