Market and Regulatory Data Feeds — Zinin M2M Hub

Imovirtual Portugal Real Estate Listings

imovirtual-lisbon

Read-only

Pull live apartment and house listings straight from Imovirtual.com — Portugal's biggest real-estate classifieds portal — by deal type, property type and city. No login, no browser, no proxies. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Imovirtual.com location path segment(s), e.g. "lisboa/lisboa" (district/council) for the city of Lisbon.	lisboa/lisboa
`deal_type`	No	`comprar` for sale listings, `arrendar` for rentals.	comprar
`max_items`	No	Maximum number of listing rows to return in this run.
`max_pages`	No	How many result pages to walk before stopping.
`property_type`	No	`apartamento` for flats, `casa` for houses.	apartamento

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds useful behavioral details like 'No login, no browser, no proxies' and 'live' listings. It also mentions cost, which is beyond structured annotations, but does not detail output structure or pagination behavior.

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, followed by concise value propositions. Every sentence serves a purpose, and it is compact.

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?

Despite no output schema, the description clearly states it returns listings, and the schema defines pagination and count parameters. It is largely complete for a read-only scraping tool, though it lacks details about returned fields.

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 description coverage is 100%, so parameters are fully documented in the schema. The description's mention of 'deal type, property type and city' adds no meaning beyond existing parameter descriptions. Baseline of 3 is appropriate.

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 Imovirtual.com, a specific resource, and identifies key filters (deal type, property type, city). This distinguishes it from sibling tools focused on other real estate portals/countries.

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 that this is for Imovirtual.com, Portugal's real estate portal, implying its use case. It does not mention explicit alternatives or exclusions, but the context is unambiguous given the title and description.

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?