Skip to main content
Glama
Gov Tenders & Grants MCP

Gov Tenders & Grants MCP

TED Tenders Daily: EU procurement notices from Tenders

publicrecords--eu-ted-notices-scraper
Read-only

Search and retrieve EU procurement notices from TED with buyer, CPV code, value, deadline, and source link so you can identify relevant public tenders.

Instructions

TED Tenders Daily: EU procurement notices from Tenders. Which EU tenders were published today? Returns TED (Tenders Electronic Daily) notices with buyer, CPV, value, deadline and source link.

When to use: Use when you need EU procurement notices from TED (Tenders Electronic Daily) with buyer, CPV code, value and deadline.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "publicrecords/eu-ted-notices-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/eu-ted-notices-scraper

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publicrecords--eu-ted-notices-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNoOptional Common Procurement Vocabulary code (e.g. 72000000). Mapped to classification-cpv. Ignored if expertQuery is set.
scopeNoTED scope: ALL (archive) or ACTIVE (currently open). Default ALL.ALL
keywordsNoOptional. Mapped to TED expert-search FT~"…" full-text. Ignored if expertQuery is set.
maxItemsNoMaximum notice rows to push to the default dataset.
noticeTypeNoOptional eForms notice-type filter (e.g. cn-standard, can-standard, pin-only, pin-cfc-standard). Ignored if expertQuery is set.
expertQueryNoOptional raw TED Expert Search expression. When set, overrides keywords / dates / noticeType / cpv / buyerCountry filters (you must include SORT BY yourself if desired). Example: buyer-country=DEU AND PD>=20260101 SORT BY publication-date DESC
buyerCountryNoOptional ISO 3166-1 alpha-3 buyer country (e.g. DEU, FRA, NLD). Mapped to buyer-country. Ignored if expertQuery is set.
publicationDateToNoOptional. Converted to TED PD<=YYYYMMDD. Ignored if expertQuery is set.
publicationDateFromNoOptional. Default: 14 days ago. Converted to TED PD>=YYYYMMDD. Ignored if expertQuery is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and destructive=false; the description adds that each call starts a new Apify Actor run under the caller's own account with their APIFY_TOKEN, which effectively explains the idempotentHint=false behavior and hints at per-run cost. It also discloses the return shape (dataset rows plus run and dataset IDs for paging), though it does not state what happens when a run yields zero notices or how long a run typically takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core question ('Which EU tenders were published today?') followed by clearly labeled Returns/Behavior/Docs sections. The opening sentence restates the title almost verbatim, and the docs URL plus actor slug are somewhat redundant given the tool name, but overall there is little wasted prose.

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 9-parameter, no-required-param scraper with no output schema, the definition covers what it returns (one row per result plus run/dataset IDs for paging), how it executes (hosted Apify MCP gateway, caller's token), and its read-only nature. Nothing an agent needs in order to call it correctly is missing.

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% and the parameter docs are already detailed (CPV mapping to classification-cpv, date conversion to TED PD>=YYYYMMDD, expertQuery overriding all filters). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — returns TED (Tenders Electronic Daily) EU procurement notices with buyer, CPV, value, deadline and source link. The domain (EU TED) is named explicitly, which distinguishes it from the US/UK tender siblings without needing their schemas.

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 'When to use' block gives a clear triggering condition (needing EU TED notices with buyer, CPV, value, deadline). It stops short of naming alternatives such as uk-find-a-tender-scraper or usaspending-awards-scraper for non-EU jurisdictions, or explaining when to prefer expertQuery over the mapped filters.

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