Skip to main content
Glama

Hilma

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hilma Recent

hilma_recent
Read-onlyIdempotent

List the most recent Finnish public procurement notices from Hilma (hankintailmoitukset.fi) — new government tenders, julkiset hankinnat, and contract notices published in Finland over the last N days (default 7). Convenience wrapper over hilma_search for "what new Finnish tenders were published this week" style questions; supports national-only and plans-excluded views.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoNumber of notices to return (1–100). Default 20.
daysNoLook-back window in days (1–365). Default 7.
_apiKeyNoOptional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products → avp-read → Subscribe).
exclude_plansNotrue → published notices only, procurement plans filtered out.
national_onlyNotrue → only national (below-EU-threshold) procurement notices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-hilma-api-key",
-    "days": 7,
-    "top": 20
-  },
-  {
-    "_apiKey": "your-hilma-api-key",
-    "days": 30,
-    "exclude_plans": true,
-    "national_only": true
-  }
-]New value: +[
+  {
+    "days": 7,
+    "top": 20
+  },
+  {
+    "days": 30,
+    "exclude_plans": true,
+    "national_only": true
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-hilma-api-key",
+    "days": 7,
+    "top": 20
+  },
+  {
+    "_apiKey": "your-hilma-api-key",
+    "days": 30,
+    "exclude_plans": true,
+    "national_only": true
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds that it is a convenience wrapper over hilma_search and has a default lookback, but it does not disclose auth needs, rate limits, or return formatting, leaving some behavioral gaps.

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: it first names the tool's resource and source, then adds usage framing and supported views. Every clause contributes to understanding the tool's scope.

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 simple read-only list tool with rich annotations, full parameter coverage, and no output schema, the description provides enough context: source, recency window, wrapper relationship, and view options. No critical agent-facing information is missing.

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 description coverage is 100%, so all five parameters are fully documented in the schema. The description adds only surface-level meaning by mentioning default days and view flags; it does not add syntax or constraints beyond what the schema provides, so baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('most recent Finnish public procurement notices from Hilma') with source domain and examples. It distinguishes itself from sibling hilma_search by calling itself a convenience wrapper for recent-tender questions.

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 routes 'what new Finnish tenders were published this week' style questions to this tool and names hilma_search as the underlying/alternative tool. It also notes supported views (national_only, exclude_plans), giving clear context for use.

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

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