Skip to main content
Glama

Netherlands Tenders

Nl Tender Recent

nl_tender_recent
Read-onlyIdempotent

List the latest Dutch government tenders and contract awards published on TenderNed (Netherlands public procurement / aanbestedingen platform) in the last N days. Great for monitoring new Dutch contract notices, fresh award announcements (gegunde opdrachten), and upcoming bid deadlines. Optionally filter to one notice type (contract notice, award, prior announcement, rectification, market consultation, modification). Returns shaped notices newest-first with id, title, buyer, closing deadline, days until closing, and TenderNed URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days (1-90). Default 7 — notices published in the last week.
pageNoZero-based results page for pagination. Default 0.
limitNoNumber of notices to return (1-50). Default 10.
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: +[
      +  {
      +    "days": 7,
      +    "notice_type": "award"
      +  },
      +  {
      +    "days": 30,
      +    "limit": 25
      +  }
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. Description adds that results are shaped and sorted newest-first, with specific output fields, providing useful behavioral context 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?

Single paragraph under 100 words, front-loaded with purpose, followed by optional filtering and output format. Every sentence adds value; no redundancy.

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 (4 optional params, no output schema), the description fully covers output fields, default behaviors, and pagination, making it complete for agent use.

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?

All parameters have schema descriptions (100% coverage). Description adds default values (days=7, limit=10) and expands notice_type options with examples, going beyond schema alone.

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?

Clearly states it lists the latest Dutch government tenders/contract awards from TenderNed in the last N days, and contrasts with sibling tools like nl_tender_search for broader querying.

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 frames it as a monitoring tool for new notices and provides filtering options, but does not directly state when not to use it or recommend sibling tools for other use cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.