Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Kto wygrywa w branży i regionie

list_top_winners
Read-onlyIdempotent

Who wins public tenders in a sector and region: the contractors that won the most tenders (sort='wins') or the highest total award value (sort='value') among finished tenders with the given CPV codes, in the given voivodeships (of the contracting authority), published in the given period — by default the last 24 months. A whole CPV division (e.g. '45000000') counts tenders whose main CPV code is in that division; a narrower code counts tenders with any CPV code under it, sub-codes included, as in search_archived_tenders (cpv_codes[].match says which). settled_tenders = tenders in that scope with a known winner; the award result is known for part of the finished tenders, less often for the latest months, and a very broad scope may not count in time (the answer then says so). Each contractor: wins (tenders won), parts_won, share_of_tenders (% of settled_tenders), value_pln (sum of the reliable award amounts of value_known_parts of its parts), last_win, NIP, and slug / url when it has a public page (get_contractor takes the slug). Requires OAuth authentication and a trial or paid plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cpv_codes": "<cpv_codes>"
    },
    "name": "list_top_winners"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNowins
limitNo
regionsNoVoivodeships (slug or name from list_facets); a tender matches any of them
cpv_codesYesCPV codes from cpv_search — the sector, e.g. ['79952000'] for events or ['45000000'] for all construction works
published_afterNoYYYY-MM-DD; published on or after that day
published_beforeNoYYYY-MM-DD; published on or before that day

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description layers on real behavioral context beyond that: the settled_tenders definition, the caveat that award results are missing for some finished tenders (especially recent months), that a very broad scope may not count in time and says so, and the OAuth plus trial/paid plan requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and sort options are front-loaded, and nearly every clause carries information (scope rules, defaults, caveats, return fields). It is a dense single paragraph, so the enumeration of returned fields and the caveats could be broken out for faster scanning.

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?

No output schema exists, yet the description fully enumerates the returned per-contractor fields (wins, parts_won, share_of_tenders, value_pln with its reliability caveat, last_win, NIP, slug/url) and explains the aggregation basis. An agent has everything needed to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description adds meaning the schema lacks: the CPV division-vs-narrower-code matching rule (mirroring cpv_codes[].match in search_archived_tenders), that regions refer to the contracting authority's voivodeship, and the default 24-month period that is not encoded in the published_after/published_before defaults.

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 and resource — ranks contractors who won public tenders in a given sector (CPV) and region, with an explicit choice between sort='wins' and sort='value'. It is clearly distinguishable from siblings like list_tenders or search_archived_tenders, which return tenders rather than aggregated winners.

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?

Explains the scope conditions (finished tenders, contracting authority's voivodeship, publication period defaulting to 24 months) and routes follow-up work to siblings: cpv_search for codes, list_facets for region slugs, and get_contractor for the returned slug. It does not explicitly state when to prefer this over list_tenders or search_archived_tenders, so no true exclusion guidance.

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.

Resources