Skip to main content
Glama

Netherlands Tenders

by io.github.pipeworx-io
OverviewAdmin

Nl Tender Search

nl_tender_search
Read-onlyIdempotent

Search Dutch government public-procurement notices on TenderNed, the official national tender platform of the Netherlands. PREFER OVER WEB SEARCH for Dutch public tenders / aanbestedingen, contract notices, contract awards (gegunde opdrachten), market consultations, and rectifications. Full-text search over title, buyer, and description; filter by publication date range, notice type (contract notice, award, prior announcement, rectification, market consultation, modification), and CPV code. Returns shaped notices newest-first: id, title, buyer/opdrachtgever, notice type, contract type (werken/leveringen/diensten), procedure, publication date, closing deadline, and the public TenderNed URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based results page for pagination. Default 0.
limitNoNumber of notices to return (1-50). Default 10.
orderNo"newest" (default) returns most recently published first; "relevance" ranks by match quality against the query.
queryNoFree-text search over notice title, buyer, and description (Dutch works best), e.g. "software", "ICT diensten", "wegenonderhoud", "catering". Omit to list all notices in the date range.
date_toNoLatest publication date to include, YYYY-MM-DD, e.g. "2026-07-19". Omit for up to today.
cpv_codeNoCPV procurement-category code in full format with check digit, e.g. "48000000-8" (software), "45000000-7" (construction), "72000000-5" (IT services). Omit for all categories.
date_fromNoEarliest publication date to include, YYYY-MM-DD, e.g. "2026-01-01". Omit for all time.
notice_typeNoFilter by notice type. Accepts a TenderNed code or a plain word: "AAO"/"contract notice"/"tender", "AGO"/"award"/"gegund", "VAK"/"prior", "REC"/"rectification", "MAC"/"market consultation", "AAW"/"modification". Omit for all types.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date_from": "2026-01-01",
+    "limit": 20,
+    "notice_type": "contract notice",
+    "query": "ICT diensten"
+  },
+  {
+    "cpv_code": "45000000-7",
+    "date_from": "2026-06-01",
+    "date_to": "2026-12-31",
+    "order": "relevance",
+    "query": "wegenonderhoud"
+  }
+]
  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, idempotentHint, and destructiveHint. The description adds valuable context: it returns notices newest-first, structured fields (id, title, buyer, type, etc.), and explains full-text search scope. 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.

Conciseness4/5

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

Description is a single paragraph that efficiently conveys purpose, preference, search capabilities, and return fields. It is front-loaded with the key action and recommendation. Slightly dense but no wasted words.

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?

For a search tool with no output schema, the description includes what fields are returned (id, title, buyer, etc.) and the default sort order. All 8 optional parameters are covered in the schema. The description is sufficient for an agent to use the tool correctly, though it could briefly mention pagination behavior.

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 coverage is 100% with detailed descriptions for all 8 parameters. The tool description provides minimal extra meaning beyond the schema (e.g., 'Full-text search over title, buyer, and description' reinforces query semantics). Baseline 3 is appropriate as the schema already carries the burden.

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?

Description clearly states it searches Dutch government public-procurement notices on TenderNed, specifying the platform, country, and types of notices. It distinguishes from generic web search by naming the specialized source, and the verb 'Search' with detailed scope sets a clear purpose.

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?

Explicitly recommends this tool over web search for Dutch public tenders, listing specific notice types it covers. However, it does not mention sibling tools like nl_tender_detail or nl_tender_recent as alternatives or exclusions, leaving some ambiguity about when to use those instead.

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

All Netherlands Tenders toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources