Atlas Przetargów
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLAS_API_KEY | No | Optional key for `/api/llm/*` endpoints (AI summaries). Without it, the server still works with full public data | |
| ATLAS_API_BASE | No | API root. Useful for staging or self-hosted Atlas | https://atlasprzetargow.pl |
| ATLAS_TIMEOUT_MS | No | Request timeout | 20000 |
| ATLAS_MAX_RETRIES | No | Retry count for 429 / 5xx / timeouts | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tendersA | Search public procurement tenders from BZP (Biuletyn Zamówień Publicznych) and TED (Tenders Electronic Daily) via Atlas Przetargów. Returns a list with titles, buyers, locations, CPV codes, estimated values and deadlines. Use for queries like 'aktywne przetargi budowlane w Warszawie', 'zamówienia IT powyżej 500k PLN', 'co kupuje ZUS'. |
| get_tenderA | Retrieve detailed information about a specific Polish public tender by its ID. Returns buyer, location, deadlines, estimated value, CPV codes, contractor (if awarded), notice type and a content excerpt. Optionally includes AI-generated summary points (requires ATLAS_API_KEY). |
| get_buyerA | Fetch a profile of a Polish public procuring entity (zamawiający) by its NIP (tax ID). Returns name, location, statistics, recent tenders, and top winning contractors. Use for due diligence on who buys what and from whom. |
| get_contractorA | Fetch a profile of a Polish tender contractor by its NIP. Returns name, location, total wins, total value and top buyers they win tenders from. |
| search_entitiesA | Search Polish public procurement entities (buyers / zamawiający) or contractors (wykonawcy) by name. Returns a list with NIP, location and volume. Useful to find the NIP for get_buyer / get_contractor tools. |
| get_category_statsA | Retrieve aggregate statistics for a CPV category: count, average/median value, average number of offers, average deadline period. Based on historical BZP+TED data. Useful for market sizing and competitive benchmarking. |
| get_province_statsA | Retrieve aggregate tender statistics by Polish province (all 16 voivodeships) or drill down to a specific city (top buyers, top CPV categories). Without arguments returns the full province ranking. |
| search_cpvA | Look up CPV (Common Procurement Vocabulary — EU procurement category) codes by Polish keyword. Use this before search_tenders to find the right CPV filter. Returns code, name, division, and historical tender count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-tender | Przeprowadza kompleksową analizę ogłoszenia BZP/TED: kluczowe warunki, kryteria oceny, ryzyka, terminy, wadium. |
| buyer-due-diligence | Przeprowadza analizę zamawiającego (procuring entity) na podstawie danych Atlas Przetargów: historia, typowi wykonawcy, wzorce, red flagi. |
| find-opportunities | Wyszukuje aktywne przetargi dopasowane do profilu firmy w danej kategorii CPV, lokalizacji i przedziale wartości. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| atlas-glossary-index | Indeks 90+ terminów polskiego prawa zamówień publicznych z atlasprzetargow.pl/slownik |
| atlas-knowledge-index | Indeks artykułów merytorycznych o zamówieniach publicznych w PL |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, get_buyer retrieves buyer profiles, get_tender fetches specific tender details, and search_tenders performs broader searches, each targeting different resources and actions. The descriptions explicitly differentiate their functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern, such as get_buyer, search_tenders, and get_category_stats. This uniformity enhances readability and predictability, with no deviations in naming conventions across the set.
With 8 tools, the count is well-scoped for the server's purpose of Polish public procurement analysis. Each tool earns its place by covering distinct aspects like entity profiles, tender searches, and statistical data, avoiding both thinness and overload.
The tool set provides complete coverage for the domain, including CRUD-like operations such as fetching entities and tenders, searching with filters, and retrieving statistical insights. There are no obvious gaps, as it supports due diligence, market analysis, and competitive benchmarking workflows.