Skip to main content
Glama

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

TableJSON 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
    • 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"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true. The description adds value by detailing return format (newest-first, specific fields), free-text search behavior, and the scope of coverage. It does not contradict annotations.

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?

The description is well-structured: it opens with purpose, then usage preference, coverage, parameter hints, and return format. It is slightly verbose but every sentence adds information appropriate for a complex 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 tool has 10 parameters, no output schema, and moderate complexity, the description is thorough. It explains the tool's scope, preference over web search, parameter usage, and return structure, leaving no major gaps.

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?

Schema coverage is 100%, so baseline is 3. The description adds contextual meaning beyond the schema, such as 'Danish terms work best' for query and guidance on obtaining CVRs from prior search results. These enrich parameter understanding.

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 clearly states the verb 'Search' and the resource 'Danish government public-procurement notices on udbud.dk'. It specifically covers all notice types for Danish tenders. While it doesn't explicitly differentiate from sibling tools like dk_tender_detail or dk_tender_recent, the scope is distinct enough to imply usage.

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 recommends preferring this tool over web search for Danish public tenders, listing covered categories. However, it does not provide guidance on when to use this tool versus sibling tools (dk_tender_detail, dk_tender_recent), which are present in the sibling list.

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