Skip to main content
Glama

Hilma Notice Lookup

hilma_notice_lookup
Read-onlyIdempotent

Look up a single Finnish public procurement notice on Hilma (hankintailmoitukset.fi) by its Hilma notice number (e.g. "2026-012345") or index document id. Returns the index metadata for that notice, buyer organisation, publication date, CPV codes, procurement project id, and national/framework/dynamic-purchasing flags.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notice_number": "2026-012345"
    },
    "name": "hilma_notice_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoIndex document id from a previous hilma_search result. Provide this or "notice_number".
_apiKeyNoOptional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products -> avp-read -> Subscribe).
notice_numberNoHilma notice number, e.g. "2026-012345". Provide this or "id".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products → avp-read → Subscribe)."New value: +"Optional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products -> avp-read -> Subscribe)."
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "_apiKey": "your-hilma-api-key",
      -    "notice_number": "2026-012345"
      -  },
      -  {
      -    "_apiKey": "your-hilma-api-key",
      -    "id": "abc123def456"
      -  }
      -]New value: +[
      +  {
      +    "notice_number": "2026-012345"
      +  },
      +  {
      +    "id": "abc123def456"
      +  }
      +]
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-hilma-api-key",
      +    "notice_number": "2026-012345"
      +  },
      +  {
      +    "_apiKey": "your-hilma-api-key",
      +    "id": "abc123def456"
      +  }
      +]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to restate the safety profile. It adds useful context by specifying that the result is index metadata plus buyer, publication date, CPV codes, project id, and procurement flags rather than the full notice, though it does not discuss API-key or error behavior.

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 two compact sentences and front-loads the core action before listing return fields. Every clause contributes either lookup scope or useful output context, with no redundant wording.

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 simple read-only lookup with no output schema and a fully documented input schema, the description provides enough detail about the action, identifiers, and return fields. Minor gaps remain around whether exactly one identifier is required despite zero required parameters, and how conflicts between id and notice_number are handled.

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?

The input schema has 100% description coverage, and it already explains notice_number, id, and the optional _apiKey. The description repeats the identifier examples and types but adds little meaning beyond what the schema provides, so the baseline of 3 applies.

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 and resource: look up a single Finnish public procurement notice on Hilma. It also identifies the exact lookup keys, notice number or index document id, making clear this is an identifier-based single-record lookup rather than a search or list operation.

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

Usage Guidelines3/5

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

The description implies usage when the agent already has a notice number or an index document id, especially by noting that the id comes from a previous hilma_search result. However, it does not explicitly say when to use hilma_search or hilma_recent instead, nor does it state what to do when no identifier is available.

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.