Skip to main content
Glama

Tu Lugar

by com.tulugar

Search Listings

search_listings
Read-only

Search real estate listings. Filter by city, price, bedrooms, property type, or a specific agency/company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name, e.g. "Asunción"
sortNo
limitNoMax 20
companyNoAgency/company NAME to list only their properties, e.g. "RE/MAX Urbana" (resolved automatically; punctuation/accents ignored).
bedroomsNo
buildingNoBuilding/tower NAME to list the actual units for sale/rent in it, e.g. "Petra Tower" (punctuation/accents ignored). Use this — not search_projects — when the user wants the real listings in a named building.
amenitiesNoComma-separated amenities/features the property must have, in the user's own words and language, e.g. "piscina, cochera" or "pool, gym". Common ones: pool/piscina, gym/gimnasio, garden/jardín, balcony/balcón, terrace/terraza, parking/cochera, furnished/amoblado, airConditioning/aire, security/seguridad, elevator/ascensor, bbq/parrilla/quincho, laundry/lavadero. Multiple = must have all.
max_priceNo
min_priceNo
listing_typeNo
neighborhoodNo
property_typeNoapartment, house, land, commercial

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so description aligns. No additional behavioral details beyond filtering, such as pagination, sorting, or default limits. Acceptable but minimal.

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?

Single, front-loaded sentence that efficiently conveys purpose and key filters. Could add more context without becoming verbose, but current length is reasonable.

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?

No output schema provided; description omits result structure, sorting defaults, or pagination info. For a parameter-rich search tool, this lacks completeness.

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 50%; description mentions several filter fields (city, price, bedrooms, property type, company) but does not elaborate on all 12 parameters. Adds some context but not comprehensive.

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?

Clearly states 'Search real estate listings' with a specific verb and resource. Lists filter criteria (city, price, bedrooms, property type, company), distinguishing it from sibling tools like search_agents or search_projects.

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?

Implies usage for general listing search but lacks explicit when-to-use or alternatives. No guidance on when not to use or comparisons with similar sibling tools like 'fetch' or 'get_listing'.

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

All Tu Lugar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap between 'search' and 'search_listings', and between 'fetch' and 'get_listing'. However, descriptions effectively differentiate them.

Naming Consistency3/5

Naming follows multiple patterns: verb_noun (create_listing), noun (closing_costs), get_*, search_*, my_*. While each pattern is internally consistent, the mix reduces overall consistency.

Tool Count3/5

39 tools is relatively high, but they cover a broad set of real estate functionalities. The count feels slightly heavy but is justified by the domain scope.

Completeness5/5

The tool set covers the full lifecycle of listings (CRUD, promotion, sharing), account management, search with multiple filters, market data, guides, and lead management. No obvious gaps for the platform's purpose.

Resources