Skip to main content
Glama

Udbud Dk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dk Tender Recent

dk_tender_recent
Read-onlyIdempotent

List the latest Danish government tenders and contract awards published on udbud.dk (Denmark's national public-procurement portal) in the last N days. Great for monitoring new Danish contract notices, fresh awards (tildelinger), direct awards, and upcoming bid deadlines — including national below-EU-threshold udbud that TED misses. Optionally restrict to one notice type or to currently active procurements. Returns shaped notices newest-first with notice id, title, buyer with CVR, CPV code, estimated value in DKK, deadlines, and the public udbud.dk URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days (1-90). Default 7 — notices published in the last week.
pageNoONE-based results page for pagination (first page is 1). Default 1.
limitNoNumber of notices to return (1-50). Default 10.
statusNo"all" (default) includes awards and closed notices; "active" restricts to currently open procurements.
notice_typeNoFilter by notice type. Accepts an udbud.dk code or a plain word: "EU_UDBUD"/"eu", "NATIONALE_UDBUD"/"national", "TILDELINGER"/"award", "DIREKTE_TILDELINGER"/"direct award", "FORHAANDSMEDDELELSER"/"prior information", "MARKEDSDIALOGER"/"market dialogue", "FORVENTET_INDKOEB"/"planned", "KONTRAKTAENDERINGER"/"modification". Omit for all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 7,
+    "limit": 10
+  },
+  {
+    "days": 30,
+    "limit": 25,
+    "notice_type": "award",
+    "status": "all"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable behavioral context: returns shaped notices newest-first, includes fields like buyer with CVR, CPV, DKK value, and mentions the source udbud.dk. No contradictions with annotations.

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 paragraph that front-loads the primary action. Every sentence adds value, covering purpose, use case, optional filters, and output fields without waste.

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 no output schema, the description thoroughly explains the return format (fields like notice id, title, buyer with CVR, CPV, DKK value, deadlines, URL). It also provides context about coverage of national below-EU-threshold notices, making it fully self-contained for a list tool.

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% (all 5 parameters documented). The description merely restates the option to restrict by notice type or status, adding no new semantic meaning beyond the parameter descriptions. Baseline score of 3 is appropriate.

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 the tool lists the latest Danish tenders from udbud.dk within N days. It specifies the content (awards, direct awards, deadlines) and explicitly distinguishes itself from TED, making its purpose unique and distinct from siblings like dk_tender_search.

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 explains it is great for monitoring new notices and includes national below-EU-threshold udbud. It implies use for time-bound recent listings but does not explicitly exclude alternative use cases or compare to sibling dk_tender_search.

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