Skip to main content
Glama

Doffin

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Doffin Notice

doffin_notice
Read-onlyIdempotent

Fetch the full document for one Norwegian public-procurement notice from Doffin (Norway's official government tender database, doffin.no) by its Doffin id, e.g. "2023-100282". Returns the complete notice as published — buyer, description, CPV codes, deadlines, values in NOK, and award details where present — plus the public doffin.no URL. Use ids from doffin_search or doffin_recent results. Requires a free Doffin API key via _apiKey when a platform key is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_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.
doffin_idYesDoffin notice id, e.g. "2023-100282" (format: year-number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-doffin-api-key",
-    "doffin_id": "2024-150042"
-  }
-]New value: +[
+  {
+    "doffin_id": "2024-150042"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-doffin-api-key",
+    "doffin_id": "2024-150042"
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, setting a baseline. The description adds value by describing the return content (buyer, CPV codes, deadlines, NOK values, award details, URL) and the prerequisite API key, which extends beyond the annotations. Minor gap: no mention of rate limits or error behavior, but not essential given the safe read-only nature.

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?

Two sentences, front-loaded with the core action and target. No filler; each clause serves a purpose (what, return content, source of ids, key requirement). Ideal length for the tool's simplicity.

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?

For a fetch-by-id tool with no output schema, the description fully covers what the agent needs: what it does, what it returns, how to obtain the id, and authentication prerequisites. Nothing essential is missing.

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 parameters are documented. The description reinforces by providing a concrete example ('2023-100282') and connecting doffin_id to the source of ids (search/recent results). This adds slight semantic enrichment beyond the schema's format note.

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 states a specific verb ('Fetch'), a specific resource ('full document for one Norwegian public-procurement notice'), and a specific identifier (Doffin id). It clearly distinguishes from sibling tools like doffin_search and doffin_recent, which are for discovery, not retrieval of a full document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to 'Use ids from doffin_search or doffin_recent results', providing direct guidance on when to use this tool versus alternatives. Also notes the API key requirement, clarifying conditional usage.

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