Market and Regulatory Data Feeds — Zinin M2M Hub

Resmî Gazete Regulatory Action Router

official-gazette-regulatory-action-router

Turn today’s allowed official publications into watchlist-linked action evidence. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema

Name	Required	Description
`watches`	Yes	One to 50 customer watch profiles. Matching is limited to official document titles and selected allowed publication classes.
`requestId`	Yes	Unique non-PII idempotency ID. A retry may reuse it only with identical input.
`maxSignals`	No	Return the highest-priority watch–document actions up to this limit.
`lookbackDays`	No	If the start date has no issue, try up to this many preceding dates. A 404 is treated only as a missing date.
`maxDocuments`	No	Fetch and validate at most this many title-matched official documents.
`publicationDate`	No	Optional YYYY-MM-DD start date. Omit to start from today's Europe/Istanbul date.
`maxTotalChargeUsd`	Yes	Hard run cap checked before any signal claim or paid delivery.

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds useful context: it is 'Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher,' and cites a per-call cost. However, it does not clarify what 'action evidence' entails or whether any state changes occur beyond what annotations imply.

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 long and front-loaded with the core purpose, followed by cost and independence disclaimer. Every sentence carries relevant information without unnecessary verbosity.

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

Completeness2/5

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

Given the tool's complexity (7 parameters, nested watches array, no output schema), the description is too sparse to orient an agent. It leaves 'action evidence' undefined, does not explain what the tool returns, and omits limitations or operational details. While the schema covers parameters, the high-level description should provide more context for a tool of this sophistication.

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% description coverage for all 7 parameters, including detailed explanations for watches, keywords, matchMode, categories, reviewWindowDays, requestId, maxSignals, lookbackDays, maxDocuments, publicationDate, and maxTotalChargeUsd. The tool description adds no parameter-specific details, so the 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's core function: 'Turn today’s allowed official publications into watchlist-linked action evidence.' The verb 'turn' and the specific resource (Resmî Gazete official publications) make the purpose evident, and the 'watchlist-linked action evidence' angle distinguishes it from sibling job/property/tender trackers.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It omits exclusions, prerequisites, or comparisons to sibling tools. The only extra information is the independence disclaimer and cost, which are not usage guidelines.

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?