Skip to main content
Glama

Netherlands Tenders

by io.github.pipeworx-io
OverviewAdmin

Nl Tender Detail

nl_tender_detail
Read-onlyIdempotent

Fetch one Dutch public-procurement notice from TenderNed (Netherlands government tender platform) by its publication id, e.g. "433909". Returns the full shaped aanbesteding notice: title, buyer/opdrachtgever, complete description, notice type, procedure, legal framework, national/European scope, CPV codes with Dutch labels, NUTS region codes, keywords, award status (gegund), related publications, official PDF link, and the public TenderNed URL. Use the id from nl_tender_search or nl_tender_recent results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publication_idYesTenderNed publication id (publicatieId), e.g. "433909" or 433910.

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: +[
+  {
+    "publication_id": "433909"
+  },
+  {
+    "publication_id": 433910
+  }
+]
  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 indicate read-only, idempotent, and non-destructive behavior. The description adds value by detailing the rich return content (title, buyer, CPV codes, etc.) and mentions the PDF link and public URL, giving the agent a clear picture of what to expect beyond the 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, well-structured paragraph. It front-loads the action, follows with a comprehensive list of return contents, and ends with a usage hint. Every sentence adds necessary context without 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 tool is a simple fetcher with one parameter and no output schema, the description compensates fully by listing many return fields, specifying the platform (TenderNed) and scope (Dutch), and referencing sibling tools. It provides complete context for an agent to understand and use the tool.

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 meaning by explaining the parameter as a 'publication id', providing an example, and instructing the agent to use the id from sibling tools, which clarifies where the value originates.

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 verb 'Fetch' and the resource 'Dutch public-procurement notice from TenderNed by its publication id'. It distinguishes from siblings by specifying that the id comes from nl_tender_search or nl_tender_recent, making the tool's specific role unambiguous.

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 says to use the id from nl_tender_search or nl_tender_recent results, providing clear context for when to invoke this tool. While it does not state negatives (e.g., when not to use), the guidance is direct and practical for an agent.

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