Skip to main content
Glama

Server Details

dane.gov.pl — Poland's national open data portal (Otwarte Dane).

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
31.6% over 49 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-dane-gov-pl
GitHub Stars
0
Server Listing
dane-gov-pl

TDQS

A4/5.0

Scored across 36 tools

Disambiguation3/5

The descriptions work hard to route callers (e.g. ask_pipeworx vs ask_pipeworx_grounded vs deep_research), but real overlaps remain: ask_pipeworx and ask_pipeworx_beta are explicitly identical, and polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker / polymarket_fill_risk cover closely adjacent ground. Entity tools (entity_profile, compare_entities, recent_changes, resolve_entity) are mostly separable, but the surface still forces an agent to reason carefully about boundaries.

Naming Consistency4/5

All names are snake_case with a clear, mostly verb_noun or namespace_noun pattern (resolve_entity, search_datasets, list_subscriptions, polymarket_edges). A few are bare noun phrases (deep_research, entity_profile, dataset_details) rather than verb-led, which is a minor deviation from the dominant convention but still highly predictable.

Tool Count3/5

36 tools is on the heavy side, but the server is a broad data gateway spanning discovery, research, memory, subscriptions, prediction markets, and open-data portal access, so most tools map to a distinct capability. It sits at the borderline where the count starts to impose routing overhead on the caller.

Completeness4/5

Coverage is broad and lifecycle-complete for its domains: discovery (discover_tools, suggest_questions), routing/research (ask_pipeworx*, deep_research), entity resolution/profiling, memory (remember/recall/forget), subscriptions (subscribe/list/recent_alerts/unsubscribe), and the dane.gov.pl read surface (search_datasets, dataset_details, list_resources, resource_data, search_institutions). Only minor gaps (e.g. no explicit write/delete on the open-data side, which is expected for a read portal).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.