Market and Regulatory Data Feeds — Zinin M2M Hub

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

Name	Required	Description	Default
`region`	Yes	A Realitica region path, e.g. `Crna-Gora` (Montenegro), `Hrvatska` (Croatia), `Srbija` (Serbia), or a city drilldown like `budva/Crna-Gora`.	Crna-Gora
`deal_type`	Yes	`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_items`	No	Maximum number of listing rows to return for this deal_type/property_type/region combination.
`max_pages`	No	How many result pages to walk (25 listings per page) before stopping.
`property_type`	Yes	`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 readOnlyHint=true and destructiveHint=false. The description adds value by noting the live data source, the absence of login/browser/proxy requirements, and the per-call cost. These are useful behavioral traits beyond the annotations, though pagination behavior and result format are not disclosed.

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, front-loaded with the core purpose, and includes only essential extras (access method and cost). Every word earns its place; no noise.

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?

For a listing-retrieval tool with fully documented parameters, the description gives enough context to select it appropriately. However, there is no output schema and the description does not describe the shape or contents of the returned listings, leaving a minor gap in 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?

The input schema provides detailed descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description only references the filter dimensions (deal type, property type, region) without adding semantic detail beyond what the schema already provides.

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 pulls live apartment and house listings from Realitica.com, specifies the geographic scope (Montenegro, Croatia, Serbia), and lists the filtering dimensions (deal type, property type, region). This specific verb+resource+scope uniquely distinguishes it from sibling real-estate tools.

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 implies when to use it: when you need real estate listings from the Adriatic region via Realitica.com. It also adds practical usage context (no login, no browser, no proxies, $0.02/call). However, it does not explicitly contrast with alternative portals or mention when not to use it.

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

All Market and Regulatory Data Feeds — Zinin M2M Hub tools Inspect

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

Disambiguation2/5

Many tools have overlapping purposes, with over a dozen real-estate scrapers and half a dozen job boards differentiated only by geography. While descriptions are clear, an agent would struggle to pick the correct tool without prior knowledge of the specific site or region, leading to frequent misselection.

Naming Consistency2/5

Tool names use a mix of lowercase-hyphenated (boss-az, clinical-trials-monitor), underscore (pricing_info), and long descriptive phrases (official-gazette-regulatory-action-router). No consistent verb_noun pattern exists; some start with source domains, others with action nouns. This lack of predictability makes navigation confusing.

Tool Count3/5

36 tools is on the heavy side for a server that could have been more focused. While a 'data hub' can justify many endpoints, the high number of near-identical scrapers (12+ real estate, 6+ job boards) suggests bloat rather than well-scoped functionality. A leaner set with parameterized regional filters would be more appropriate.

Completeness2/5

The claimed domain 'Market and Regulatory Data Feeds' is poorly served: there are no stock/forex/commodity price feeds, few global regulatory sources (only FDA, SEC, EU tenders), and many tools are for job and property listings which are tangential. The set feels like a random aggregation rather than a coherent surface, with obvious gaps for core market and regulatory data.

Resources

Need Help?