Skip to main content
Glama

Doffin

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Doffin Recent

doffin_recent
Read-onlyIdempotent

List the latest Norwegian government tenders and contract awards published on Doffin (Norway's national public-procurement / offentlige anskaffelser database) in the last N days, newest first. Great for monitoring fresh Norwegian anbud, new kunngjøringer, contract award results (tildelinger), and upcoming bid deadlines. Optionally narrow to one or more notice types (tender/competition, award/result, planning, ...) or a free-text query. Each hit gets a public doffin.no notice URL attached. Requires a free Doffin API key via _apiKey when a platform key is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days (1-90). Default 7 — notices published in the last week.
pageNoResults page for pagination. Default first page.
typeNoNotice type filter — one value or an array; plain words work: "tender"/"competition" → COMPETITION, "award"/"result" → RESULT, "planning" → PLANNING, etc. Omit for all types.
limitNoNumber of hits to return (1-100). Default 10.
queryNoOptional free-text filter (Norwegian works best), e.g. "rammeavtale", "skole", "programvare".
_apiKeyNoDoffin API subscription key (free — sign up at https://dof-notices-prod-api.developer.azure-api.net/). Injected automatically when the platform key is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-doffin-api-key",
-    "days": 7,
-    "type": "RESULT"
-  },
-  {
-    "_apiKey": "your-doffin-api-key",
-    "days": 30,
-    "limit": 25,
-    "query": "rammeavtale",
-    "type": [
-      "COMPETITION",
-      "PRE_ANNOUNCEMENT"
-    ]
-  }
-]New value: +[
+  {
+    "days": 7,
+    "type": "RESULT"
+  },
+  {
+    "days": 30,
+    "limit": 25,
+    "query": "rammeavtale",
+    "type": [
+      "COMPETITION",
+      "PRE_ANNOUNCEMENT"
+    ]
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-doffin-api-key",
+    "days": 7,
+    "type": "RESULT"
+  },
+  {
+    "_apiKey": "your-doffin-api-key",
+    "days": 30,
+    "limit": 25,
+    "query": "rammeavtale",
+    "type": [
+      "COMPETITION",
+      "PRE_ANNOUNCEMENT"
+    ]
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds non-obvious behavioral context: results are ordered newest first, each hit includes a public doffin.no notice URL, and a free Doffin API key is required via _apiKey unless a platform key exists. No contradiction 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 compact and front-loaded: purpose, use-case context, filter options, output URL, and auth requirement all appear in a logical order with no redundant re-statements of schema fields. Every sentence adds selection or invocation value.

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 read-only list tool with no output schema, the description covers scope, ordering, filter flexibility, attached public URLs, and authentication. It does not spell out the exact shape of returned hits or pagination behavior, but the input schema already documents page/limit and examples, leaving only a minor completeness gap.

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%, and every parameter already has detailed descriptions including defaults, ranges, and allowed aliases. The description's mention of narrowing 'by notice types' or using 'a free-text query' mirrors the schema rather than adding new parameter-specific semantics, so the high-coverage baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: 'List the latest Norwegian government tenders and contract awards published on Doffin' within a lookback window, newest first. It clearly conveys the recency-oriented scope, but it does not explicitly distinguish itself from sibling tools like doffin_search or doffin_notice, so it stops short of a 5.

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 provides clear usage context: 'Great for monitoring fresh Norwegian anbud, new kunngjøringer, contract award results (tildelinger), and upcoming bid deadlines.' This tells an agent when the tool is appropriate, though it does not state when to prefer an alternative such as doffin_search, so it lacks explicit exclusions.

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

All Doffin 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