Skip to main content
Glama

Data Calgary

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

DataCalgary MCP — Calgary open data (data.calgary.ca, Socrata SODA API).

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
39.7% over 43 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-data-calgary
GitHub Stars
0
Server Listing
data-calgary

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Several clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all compete as research/routing entry points, while entity_profile, recent_changes, compare_entities, and validate_claim overlap for company facts. The polymarket_* family has six tools with distinct sub-purposes, but the sheer volume and shared framing make tool selection non-trivial. Descriptions help, but boundaries remain fuzzy enough to cause misselection.

Naming Consistency4/5

Most tools follow a readable snake_case convention with predictable action or resource patterns (calgary_query, entity_profile, list_subscriptions, polymarket_edges). Minor deviations exist: remember/recall/forget are bare verbs, while pipeworx_feedback and pipeworx_trending are resource-first, and the ask_pipeworx variants use suffixes. Overall the naming is consistent enough to be navigable.

Tool Count2/5

With 34 tools, this is a heavy set that demands significant selection effort, especially since the server is named Data Calgary but only three tools (calgary_datasets, calgary_query, calgary_recent) actually address Calgary open data. The rest are broad Pipeworx platform tools spanning prediction markets, memory, subscriptions, AI visibility, and dependency scanning. The count feels mismatched to the apparent narrow Calgary branding and creates avoidable cognitive load.

Completeness4/5

For the Calgary open-data portion, the surface covers discovery (calgary_datasets), raw SoQL access to any resource (calgary_query), and common recent records (calgary_recent), which is a complete read-only lifecycle for open data. The broader platform adds discovery, execution, memory, subscriptions, and feedback, leaving few obvious dead ends. Minor gaps include no dedicated Calgary dataset metadata/catalog listing beyond keyword search, but agents can work around this via calgary_datasets.

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": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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 (\"when-will-bitcoin-hit-150k\"), 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."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_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • 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 (\"when-will-bitcoin-hit-150k\"), 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_spread1 field changed
      • 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

  • mcp-data-kcmo

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for accessing Kansas City, MO open data through the Socrata SODA API. Enables querying and retrieving public datasets from data.kcmo.org.
    135 npm
    MIT

  • Sofia Data MCP

    manevpe
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for querying and analyzing urban data from the Sofia municipality CKAN portal. Provides tools for dataset search, retrieval, preview, summarization, and faceted browsing.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources