Market and Regulatory Data Feeds — Zinin M2M Hub

Krisha.kz Kazakhstan Real Estate Listings

krisha-kz

Read-only

Pull live apartment and house listings straight from Krisha.kz — Kazakhstan'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
`queries`	Yes	One entry per search, format "deal:type:city". deal is `sale` or `rent`, type is `apartment` or `house`, city is a Krisha.kz city slug (e.g. `almaty`, `astana`, `shymkent`). Example: "sale:apartment:almaty".
`max_items`	No	Maximum number of listing rows to return across ALL queries combined, in this run.
`max_pages`	No	How many result pages to walk for each individual query before moving on.
`maxConcurrency`	No	How many queries to run in parallel.

TDQS

A4.3/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 valuable context beyond annotations: 'No login, no browser, no proxies' discloses authentication requirements, and '$0.02/call, x402 (USDC on base)' reveals pricing and payment method—useful operational details not present in annotations.

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, each with distinct value: the first states purpose and filters, the second adds operational details (no auth, cost). It is front-loaded, free of fluff, and every clause contributes meaning.

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

Completeness5/5

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

For a read-only listings fetch tool with four params and no output schema, the description covers the data source, filter scope, access prerequisites, and cost. The agent has enough context to decide whether to invoke it and what to pass, matching the completeness bar for a filtered-list tool.

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 100%, with each parameter having a detailed description (e.g., queries format 'sale:apartment:almaty'). The description echoes filter dimensions (deal type, property type, city) but adds no new parameter-specific information, so it meets the baseline without exceeding it.

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 the verb 'Pull' and specifies the resource: 'live apartment and house listings straight from Krisha.kz' with filters for deal type, property type, and city. It clearly distinguishes itself from sibling real-estate tools by naming the specific portal and location (Kazakhstan).

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 clearly implies the tool is for Kazakhstan real estate data by naming the country and the portal, and notes operational ease ('No login, no browser, no proxies'). However, it does not explicitly state when not to use it or name alternative tools, so it falls short of the highest bar.

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?