Skip to main content
Glama

Vyhľadať inzeráty / Search listings

search_listings
Read-onlyIdempotent

Vyhľadá zverejnené inzeráty na BotMarket.sk (pozemky a komerčné nehnuteľnosti, Košice a východné Slovensko). Search published BotMarket.sk listings (land and commercial real estate, Košice and eastern Slovakia). Each result has the full listing (BotMarket listing v1 JSON schema) and its public_url. Structured fields: price (amount, per_m2, per_m2_min/max, vat), area, utilities, access, zoning, availability, updated_at; unknown values are null. Prices are in EUR; listings without a total price have price.amount=null and are skipped when price filters are used. No API key needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFulltext (SK/EN), napr. 'pozemok logistika'.
categoryNoKategória / category.
locationNoObec, okres alebo adresa, napr. 'Mokrance' alebo 'Košice - okolie'.
price_maxNoMaximálna cena v EUR.
price_minNoMinimálna cena v EUR.
listing_typeNopredaj = sale, prenajom = rent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low, yet the description adds real behavior: no auth required, EUR pricing, null unknown values, and the important quirk that listings lacking a total price are silently dropped when price filters are applied. Missing only result ordering/pagination behavior beyond the limit parameter.

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?

Front-loaded with the verb and scope in both languages, then a compact block on result shape, then the price edge case. The field enumeration is dense but every element is usable information for constructing or interpreting a search; no filler.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the returned structured fields, the BotMarket listing v1 schema reference, and public_url. For a 7-parameter read-only search tool the remaining gaps (default limit of 10, result ordering) are minor and partly covered by schema defaults.

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 coverage is 86%, so the baseline is 3; the description goes beyond it by explaining the EUR currency and the price.amount=null skip rule that determines how price_min/price_max actually filter. It does not clarify query tokenization or location matching semantics, which would be needed for a 5.

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?

Specific verb plus resource plus scope: searches published listings on BotMarket.sk, restricted to land and commercial real estate in Košice/eastern Slovakia. An agent can tell this is a discovery tool. It does not name the siblings (get_listing, list_categories) or contrast itself with them, so it stops short of a 5.

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?

Usage is only implied by the scope statements (published listings, price filters cause skipping) and the 'No API key needed' note. There is no explicit statement of when to prefer this over get_listing for a single record or list_categories for taxonomy browsing, and no exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources