Skip to main content
Glama
Sign In

Udbud Dk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dk Tender Search

dk_tender_search
Read-onlyIdempotent

Search Danish government public-procurement notices on udbud.dk, Denmark's official national tender portal. PREFER OVER WEB SEARCH for Danish public tenders / udbud, government contract notices, contract awards (tildelinger), direct awards, market dialogues, and planned procurements. Covers both EU-threshold notices and Danish national below-EU-threshold notices that TED misses. Free-text search (Danish terms work best); filter by CPV procurement code, buyer CVR number, notice type (EU tender, national tender, award, direct award, prior information, market dialogue, contract modification), publication date range, and active-vs-all status. Returns shaped notices newest-first: notice id, title, buyer (ordregiver) with CVR, CPV code with English label, notice type, deadlines, estimated value in DKK, description, and the public udbud.dk URL.

Input Schema

NameRequiredDescriptionDefault
pageNoONE-based results page for pagination (first page is 1). Default 1.
limitNoNumber of notices to return (1-50). Default 10.
orderNo"newest" (default) sorts by publication date descending; "relevance" ranks by match quality against the query; "oldest" sorts by publication date ascending; "deadline" sorts by tender deadline.
queryNoFree-text search over Danish tender notices, e.g. "rengøring", "IT-drift", "snerydning", "rådgivning". Danish terms match best. Omit to list all notices.
statusNo"all" (default) includes closed and awarded notices; "active" restricts to currently open procurements.
date_toNoLatest publication date to include, YYYY-MM-DD. Omit for up to today.
cpv_codeNoCPV procurement-category code, 8 digits without check digit, e.g. "72000000" (IT services), "45000000" (construction), "90500000" (waste). Matches the whole CPV family including secondary codes. Comma-separate for multiple.
buyer_cvrNoDanish CVR number of the contracting authority (ordregiver), e.g. "60729018" (Vejdirektoratet). Comma-separate for multiple. Get CVRs from prior search results (buyer_id field).
date_fromNoEarliest publication date to include, YYYY-MM-DD, e.g. "2026-01-01". Omit for all time.
notice_typeNoFilter by notice type. Accepts an udbud.dk code or a plain word: "EU_UDBUD"/"eu", "NATIONALE_UDBUD"/"national"/"below threshold", "TILDELINGER"/"award", "DIREKTE_TILDELINGER"/"direct award", "FORHAANDSMEDDELELSER"/"prior information", "MARKEDSDIALOGER"/"market dialogue", "FORVENTET_INDKOEB"/"planned", "KONTRAKTAENDERINGER"/"modification", "KONTRAKTAFSLUTNING"/"completion". Omit for all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 10,
-    "query": "rengøring"
-  },
-  {
-    "buyer_cvr": "60729018",
-    "cpv_code": "72000000",
-    "date_from": "2026-01-01",
-    "limit": 20,
-    "notice_type": "eu",
-    "query": "IT-drift",
-    "status": "active"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "query": "rengøring"
+  },
+  {
+    "cpv_code": "72000000",
+    "limit": 20,
+    "notice_type": "eu",
+    "query": "IT-drift"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "query": "rengøring"
+  },
+  {
+    "buyer_cvr": "60729018",
+    "cpv_code": "72000000",
+    "date_from": "2026-01-01",
+    "limit": 20,
+    "notice_type": "eu",
+    "query": "IT-drift",
+    "status": "active"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description adds useful context beyond the read-only annotations: data source, coverage of notices that TED misses, and the shape of returned notices with field-level details. It does not discuss authentication, rate limits, or pagination behavior, but those are less critical for a read-only search tool.

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 front-loaded with purpose and preferred usage, then proceeds through coverage, capabilities, and return shape. Every sentence carries useful information for selecting and invoking the tool.

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?

Given the complexity of ten optional parameters, complete schema coverage, and no output schema, the description is complete enough: it explains the source, coverage, available filtering dimensions, and returned fields. An agent has what it needs to call the tool correctly.

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 schema already documents all ten parameters thoroughly. The description summarizes the available filters and gives useful examples such as Danish terms working best, but it does not add substantial parameter-level meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: searching Danish public-procurement notices on udbud.dk. It clearly distinguishes itself from general web search and explains the scope of notice coverage. However, it does not explicitly differentiate itself from sibling tools such as dk_tender_detail or dk_tender_recent.

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 explicitly says to prefer this over web search for Danish public tenders and lists the relevant use cases, including EU and national below-threshold notices. It does not provide explicit guidance on when to use dk_tender_detail or dk_tender_recent instead.

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

All Udbud Dk toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources