Skip to main content
Glama

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.4/5.0
Behavior5/5

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

Annotations only provide generic hints (readOnlyHint false, openWorldHint true), but the description and schema add rich behavioral detail: per-call cost, stateful 'since last check' logic, first-run baseline behavior, rate-limit handling, and honest partial coverage. This far exceeds what annotations offer and gives the agent clear expectations.

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 that front-loads the tool's purpose, followed by a concise cost note. No wasted words; it earns its place.

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 9 parameters and no output schema, the schema descriptions comprehensively cover edge cases, billing, and behavior. The only minor gap is a lack of explicit output row format, but the description's 'get only the new ones' plus parameter context make the tool's intent complete enough.

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% with highly detailed parameter descriptions, so the baseline is 3. The main description adds only a high-level summary of filter types ('keywords, CPV codes, value threshold or region') and does not add new syntax or edge-case meaning beyond the schema.

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 a specific action ('Watch UK Find a Tender') and resource, plus an incremental filtering behavior ('newly matching... since your last check'). This distinguishes it from sibling tools like generic tender-alert or gov-tender-radar by specifying the UK source and stateful lead-alert nature.

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 a monitoring use case for new UK public tenders, and the schema enforces that at least one filter is required, which is clear usage context. However, no explicit alternatives or when-not-to-use guidance are given, so it misses the full 'when vs alternatives' standard.

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
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources