prozorro_historical_release

Pack: prozorro · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/prozorro_historical_release for the schema, then POST the same URL with its arguments for the data.

Detail for a Ukraine ProZorro tender that prozorro_get_tender can’t resolve from a human tenderID — its tenderID-to-internal-id lookup only scans the most-recently-modified few thousand records (fleet #2762/#2768), so a tenderID found via prozorro_search_tenders’ date-range browsing (e.g. a 2015 tender) comes back detail_available:false there. An internal 32-hex id ALWAYS resolves immediately regardless of age (a direct lookup, no scan needed). For a human tenderID this tries TWO live strategies before giving up: the same recently-modified scan prozorro_get_tender uses, then a bounded forward scan seeded from the DATE THE TENDERID ITSELF ENCODES (“UA-2015-02-16-…” -> search from 2015-02-16) — this finds it when the tender’s last modification happened reasonably soon after that date, and does not when a later amendment moved it far down the feed; both are live, keyless, no stored data (fleet #3244). source says which path answered; detail_available:false (never a crash, never an empty object) means neither reached it, and only the search-index summary is available.

Parameters

NameTypeRequiredDescription
idstringyesTender id — internal 32-hex (e.g. “09076ffc415e4d57ad7046aacc91b6e1”) or human tenderID (e.g. “UA-2015-02-16-000001”).

Example call

Arguments

{
  "id": "09076ffc415e4d57ad7046aacc91b6e1"
}

curl

curl -X POST https://gateway.pipeworx.io/prozorro/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"prozorro_historical_release","arguments":{"id":"09076ffc415e4d57ad7046aacc91b6e1"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('prozorro_historical_release', {
  "id": "09076ffc415e4d57ad7046aacc91b6e1"
});

More examples

{
  "id": "UA-2015-02-16-000001"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the prozorro pack
{
  "mcpServers": {
    "prozorro": {
      "url": "https://gateway.pipeworx.io/prozorro/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 19, 2026