Skip to main content
Glama
ai-engineers-guild

Apartment Hunter MCP Server

create_search_profile

Create a search profile with custom filters to automatically monitor and receive notifications for new rental apartments matching your preferences.

Instructions

Create a search profile for ongoing apartment monitoring.

The profile defines filters and preferences. The ingestion pipeline will use these profiles to fetch new apartments and send notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name in Russian, e.g. 'Алматы', 'Астана'
nameYesHuman-readable profile name, e.g. 'Алматы 2к до 300т'
roomsNoList of room counts, e.g. [1, 2]
sourcesNoSource names, e.g. ['krisha.kz']; defaults to all registered adapters
area_maxNo
area_minNo
keywordsNoSemantic search keywords for RAG matching
polygonsNoList of polygons. Each polygon is a list of [lat, lon] floats forming a closed shape.
districtsNoOptional list of district names
furnitureNoTrue=with furniture, False=without, None=any
has_photoNoOnly with photos
min_scoreNoMinimum LLM score for notifications (0.0-10.0)
price_maxNo
price_minNo
owner_onlyNoOnly from owners (no agencies)
nl_descriptionNoFree-text description for semantic re-ranking (e.g. 'светлая квартира с новым ремонтом')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully communicate behavioral traits. It only states creation and purpose but omits details like idempotency, permissions, rate limits, or side effects (e.g., whether existing profiles are overwritten). The agent lacks key safety information.

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

Conciseness4/5

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

The description is two sentences and front-loads the purpose. However, given 16 parameters, it could be more structured to highlight key parameters or defaults. Still, it is efficient and avoids unnecessary detail.

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

Completeness2/5

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

Despite high parameter count and an output schema (not detailed), the description does not explain the output (e.g., profile ID), required parameters, or defaults. For a creation tool with many options, this insufficiently prepares the agent for correct usage.

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 coverage is 75%, so baseline is 3. The description mentions 'filters and preferences' but does not elaborate on any specific parameters beyond what the schema provides. It adds no additional meaning to the parameter definitions.

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?

The description clearly states the tool creates a search profile for ongoing apartment monitoring, specifying that it defines filters and preferences for the ingestion pipeline to fetch apartments and send notifications. This distinctly sets it apart from sibling tools like list_search_profiles or delete_search_profile.

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?

The description implies usage for setting up ongoing monitoring but does not explicitly mention when to use it over alternatives like search_by_profile or when not to use it. No exclusions or alternative guidance is provided, leaving the agent to infer context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ai-engineers-guild/apartment-hunter'

If you have feedback or need assistance with the MCP directory API, please join our Discord server