Skip to main content
Glama

Market Data

by com.timzinin.api

Realitica.com Adriatic Real Estate Listings

realitica-adriatic
Read-only

Pull live apartment and house listings straight from Realitica.com — a real-estate classifieds portal covering Montenegro, Croatia and Serbia — by deal type, property type and region. No login, no browser, no proxies. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesA Realitica region path, e.g. `Crna-Gora` (Montenegro), `Hrvatska` (Croatia), `Srbija` (Serbia), or a city drilldown like `budva/Crna-Gora`.Crna-Gora
deal_typeYes`prodaja` (sale) or `najam` (long-term rent). `najam` maps to Realitica's own "Duži Najam" long-term-rental category, not its separate short-term/tourist rental listings.prodaja
max_itemsNoMaximum number of listing rows to return for this deal_type/property_type/region combination.
max_pagesNoHow many result pages to walk (25 listings per page) before stopping.
property_typeYes`stanova` (apartments) or `kuca` (houses).stanova

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description adds useful context beyond that: live listings, no authentication required, and a $0.02/call pricing model. No contradictions found.

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 two sentences: the first delivers the core function and scope, the second adds operational extras (no auth, pricing). Every clause contributes information, and the key verb appears first.

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?

Given the rich schema and the absence of an output schema, the description covers the functional purpose, geographic scope, and access constraints well. It does not describe the listing output fields, but that is not strictly required for tool selection and invocation.

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?

The input schema provides 100% coverage with descriptions for all five parameters, so the schema itself carries the semantic load. The description only restates the three key filters without adding extra parameter-level detail or examples.

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 uses a specific verb ('Pull') with a clear resource (Realitica.com listings) and geographic scope (Montenegro, Croatia, Serbia), making it easily distinguishable from sibling real-estate tools. It also mentions the three key filtering dimensions, fully covering the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about the geographic area and access method ('No login, no browser, no proxies'), but it does not explicitly name alternatives or state when not to use the tool. This is adequate for selection among siblings given the unique resource name and geography.

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

All Market Data 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

B3.4/5.0
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources