Skip to main content
Glama

Udbud Dk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dk Tender Detail

dk_tender_detail
Read-onlyIdempotent

Fetch one Danish public-procurement notice from udbud.dk (Denmark government tender portal) in full detail. Returns the shaped notice summary — title, buyer (ordregiver) with CVR, publication date, CPV code, notice type, estimated value in DKK, deadlines, lot count, execution place, tender documents — plus the complete notice text extracted from the official eForms rendering (English version when available). Requires the notice_id, notice_version, and publication_number exactly as returned by dk_tender_search or dk_tender_recent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage of the full notice text: "en" (default, machine-assisted English) or "da" (original Danish).
notice_idYesNotice UUID from search results, e.g. "14f9c6aa-740c-46ce-95a8-47df319d7de5".
max_text_charsNoMaximum characters of full notice text to return (0-30000). Default 8000. Set 0 to skip the full text and return only the summary.
notice_versionNoNotice version from search results, e.g. "01". Default "01".
publication_numberYesNotice publication number from search results (publication_number field), e.g. "00724546-2024".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "notice_id": "14f9c6aa-740c-46ce-95a8-47df319d7de5",
+    "publication_number": "00724546-2024"
+  },
+  {
+    "language": "da",
+    "max_text_chars": 8000,
+    "notice_id": "14f9c6aa-740c-46ce-95a8-47df319d7de5",
+    "notice_version": "01",
+    "publication_number": "00724546-2024"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already show readOnlyHint, idempotentHint, and openWorldHint. The description adds that the tool returns a shaped summary and the complete notice text, including language and character limit options. No contradictions, and it enhances understanding of behavior beyond 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 concise, front-loaded with purpose, and structured as a single clear paragraph. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters and no output schema, the description compensates by detailing the output fields (title, buyer, etc.) and explaining the language and character count parameters. It also ties to sibling tools, making it fairly complete for a fetch operation.

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 description adds context that parameters come from search results and provides an example. However, it does not add significant new semantic meaning beyond the schema.

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 fetches a Danish public-procurement notice in full detail, listing specific fields (title, buyer, CVR, etc.) and the source (udbud.dk). It distinguishes itself from sibling tools dk_tender_search and dk_tender_recent by requiring their output.

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?

It explains that the tool requires notice_id, notice_version, and publication_number exactly as returned by dk_tender_search or dk_tender_recent, providing clear prerequisites. It does not explicitly list when not to use or alternatives, but the context is strong.

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