Skip to main content
Glama

Market and Regulatory Data Feeds — Zinin M2M Hub

UK Public Tender Lead Alert

uk-public-tender-lead-alert

Watch UK Find a Tender for public-sector tenders newly matching your keywords, CPV codes, value threshold or region, and get only the new ones since your last check. — $0.05/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoCase-insensitive substring match against whatever buyer/delivery region or country data the notice publishes. Not a hard filter guarantee — region data is not published on every notice, and an absent field never excludes a tender on this axis alone.
cpvCodesNoMatched as a PREFIX against the tender's CPV classification code, e.g. "7211" matches "72110000". A full code with a check digit ("72000000-5") is accepted and the check digit is stripped automatically. 0-20 entries.
keywordsNoCase-insensitive substring match against the tender's title and description. 0-20 entries.
stateKeyNoA name for THIS watch, so you can run several independent tender watches from one Actor without one overwriting another's memory of what it has already billed. Scoped to your own Apify account. The prefilled value is only there so this Actor's own daily platform test has a stable, obviously-a-test name — replace it with your own watch name.
maxValueGbpNoSame GBP-only caveat as minValueGbp above.
minValueGbpNoOnly applied when the tender's published value is in GBP. A tender with a missing value, or a value published in another currency, is reported as a free, unbilled row instead of a silent guess — never excluded outright and never billed on an assumption.
emitBaselineNoWhen true (default), the first run for a new watch name writes one free, clearly-labelled row summarizing what was captured as the reference point. When false, that first run still saves the reference point — it just writes no row, for buyers who only ever want to see "new since I subscribed" and never a first-run dump.
lookbackDaysNoHow far back each run looks for updated releases. Default 1 day: the measured rate limit (12 requests before HTTP 429) covers a full 24h window in about 6 paginated requests. A wider window is honored, but is more likely to exceed the request budget mid-run and finish with honest partial coverage for that run (nothing lost — anything not read this run is picked up, and billed, on a later run).
maxNewPerRunNoCaps how many NEW matching tenders a single run delivers and charges for, even if more were found. Anything held back by this cap is never lost — it stays "new" and appears (and is billed) on a future run.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint false, openWorldHint true, idempotentHint false, and destructiveHint false. The description adds that each call costs $0.05 and that it performs incremental delta detection, which are not encoded in annotations. It does not mention rate limits or per-run billing caps, but those are detailed in the input schema descriptions, and the annotation context lowers the bar.

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 a single, focused sentence followed by a pricing tag. It front-loads the core purpose and avoids any filler or redundant information.

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 the tool's complexity (stateful watch, billing, rate limits, 9 parameters), the description covers the essential use case and cost. Critical caveats like first-run baseline, stateKey usage, and partial coverage are only in the schema descriptions, but the schema is extremely rich and available to the agent. No output schema exists, but the description clearly states the output is 'only the new ones', which is adequate.

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 the baseline is 3. The description itself does not elaborate on any parameters, but the schema for each of the 9 fields is very detailed (e.g., prefix matching for CPV codes, best-effort region matching, stateKey purpose). No compensation needed from the description.

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?

Description uses specific verb 'Watch' plus resource 'UK Find a Tender' and clearly states the tool filters for 'public-sector tenders newly matching your keywords, CPV codes, value threshold or region'. It also distinguishes its delta behavior ('only the new ones since your last check') from simpler one-shot search tools, making it distinct from sibling tools like 'tender-alert' or 'gov-tender-radar'.

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 repeated monitoring usage with 'Watch' and 'since your last check', and its UK-specific scope clearly separates it from broader tender tools. However, it does not explicitly name alternatives or state when not to use it, relying on the reader to infer that other tools cover different regions or use cases.

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

Try in Browser

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