Skip to main content
Glama

ADF: EU/UK Tenders, EU Law, Funding, Medicines, Shortages, Recalls, Sanctions, CVE, CERT, Holidays

List datasets, prices and filters

list_datasets
Read-onlyIdempotent

Free. Returns every agentdatafeed dataset with record count, last update, price per query, filters and links. Call it first to choose a dataset, then use get_sample to inspect records or query_dataset for filtered data. When to use each dataset: amsterdam-events: Use when a user asks what is on in Amsterdam on a date or in a district, plans travel, venues, staffing, security or deliveries around large events, or needs crowd sizes, road closures context or permit status before the event appears on ticket sites. security-advisories: Use when a user asks whether a CVE is actively exploited, which vulnerabilities in a vendor or product to patch first, whether it is used in ransomware campaigns, or needs CISA KEV due dates, required actions and FIRST EPSS exploit probability in one call. vulnerability-watch: Use when a user asks which recent vulnerabilities affect a server product or version, wants new critical CVEs (for example CVSS 9 or higher) for a vendor this week, or needs CVSS, affected version ranges and exploit signals (KEV, EPSS) for a CVE in the news. eu-tenders: Use when a user asks which public tenders or government contracts are open in an EU country or sector, wants bid opportunities by CPV code or keyword with a deadline, or needs to monitor what public buyers are procuring before the deadline passes. uk-tenders: Use when a user asks which UK government or public sector contracts are open to bid, wants UK tender opportunities by sector, CPV code, keyword, region or buyer with the deadline and value, or needs Find a Tender and Contracts Finder notices in one search, for example SME-friendly IT tenders in Scotland closing this month. eu-funding: Use when a user asks which EU grants, subsidies or Horizon Europe calls are open or coming up for a topic, sector or organisation type, needs the deadline, budget and call link for an EU funding opportunity, or looks for small cascade funding calls for SMEs and start-ups. cert-advisories: Use when a user asks whether the Dutch, German or French national CERT or CERT-EU has warned about a CVE, vendor or product, needs the official European advisory ID and link for a patch or NIS2 report, or wants recent government advisories that cover known exploited (CISA KEV) vulnerabilities. eu-medicines: Use when a user asks whether a medicine or active substance is authorised in the EU, who holds the marketing authorisation, what it is indicated for, whether there is a current EMA-monitored shortage, or which safety communications and referral procedures concern it. sanctions-entities: Use when a user or a KYC, AML, procurement or shipping workflow needs to check whether a company, organisation, vessel or aircraft is on the EU or OFAC sanctions list, find the programme and legal basis of a listing, or look up a sanctioned vessel by IMO number; not for screening individual people. product-recalls: Use when a user, shop, marketplace, procurement or compliance workflow asks whether a product, food, medicine, medical device, vehicle, tyre or child car seat has been recalled or flagged as unsafe in the US (FDA, CPSC, NHTSA), Canada or the UK, which allergen or hazard caused it, how serious the recall class is, whether a recalled car should not be driven, or which recalls concern a given brand, firm or vehicle make. eu-legislation: Use when a user, compliance, legal or policy workflow asks which EU regulations, directives or decisions were recently published or amended on a topic, whether an act is in force and from when, which acts amend or repeal a given CELEX number, or needs the CELEX, ELI or OJ reference and the official EUR-Lex link of an EU act. drug-shortages: Use when a user, pharmacist, hospital, wholesaler or procurement workflow asks whether a medicine or active substance is currently in short supply in the US or the EU, why, since when, when supply is expected back, which manufacturers or strengths are affected, or whether alternatives are available. public-holidays: Use when a user, scheduler, payroll, logistics or booking workflow needs to know whether a date is an official public or bank holiday in one of the covered countries or regions, which holidays fall in a date range, or how to count business days around holidays this year or next year.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
datasetsYesOne entry per dataset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "datasets": {
      +      "description": "One entry per dataset.",
      +      "items": {
      +        "properties": {
      +          "description": {
      +            "description": "Coverage, sources and fields.",
      +            "type": "string"
      +          },
      +          "fields_always_present": {
      +            "description": "Fields every record carries.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "id": {
      +            "description": "Dataset id to pass to get_sample or query_dataset.",
      +            "type": "string"
      +          },
      +          "parameters": {
      +            "additionalProperties": {
      +              "type": "string"
      +            },
      +            "description": "Filter name to meaning; pass these as query_dataset filters.",
      +            "type": "object"
      +          },
      +          "payment": {
      +            "description": "Payment method.",
      +            "type": "string"
      +          },
      +          "price_usd_per_query": {
      +            "description": "Price in USD per paid query.",
      +            "type": "string"
      +          },
      +          "query": {
      +            "description": "Paid HTTPS query endpoint.",
      +            "type": "string"
      +          },
      +          "records": {
      +            "description": "Records in the current snapshot.",
      +            "type": "integer"
      +          },
      +          "sample": {
      +            "description": "Free sample endpoint.",
      +            "type": "string"
      +          },
      +          "schema": {
      +            "description": "JSON Schema URL for the records.",
      +            "type": "string"
      +          },
      +          "title": {
      +            "description": "Display name.",
      +            "type": "string"
      +          },
      +          "updated": {
      +            "description": "Snapshot time, ISO 8601 UTC.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "price_usd_per_query",
      +          "query",
      +          "parameters"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "datasets"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the call is 'Free' (no cost/quota concern) and it discloses which fields are returned, including price per query. It does not mention rate limits or catalog staleness, so it stops short of a 5.

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

Conciseness3/5

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

Front-loaded well — purpose, return fields, and sibling routing come before the long dataset catalog. However the bulk of the text is a ~15-entry catalogue of use cases, much of it verbose and bordering on marketing copy, which inflates the definition far beyond what an agent needs at selection time.

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?

An output schema exists, so return values need no explanation, and there are no parameters to document. Given the zero-argument, read-only nature of the call, the description covers everything needed to decide to invoke it and what to do next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering inputs by describing it as returning the full catalog.

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 concrete verb and resource ('Returns every agentdatafeed dataset') and enumerates exactly what comes back (record count, last update, price per query, filters, links). It also positions itself as the entry point ahead of the named siblings, so an agent can distinguish it from get_sample and query_dataset immediately.

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

Usage Guidelines5/5

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

Explicitly says to call it first, then routes to get_sample for record inspection and query_dataset for filtered queries. The per-dataset 'when to use' paragraphs give concrete triggering conditions (e.g. CISA KEV due dates, CPV codes, IMO lookups), which is the selection guidance an agent actually needs.

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.

Resources