Skip to main content
Glama

Data Edmonton

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

DataEdmonton MCP — Edmonton open data (data.edmonton.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
38.6% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-data-edmonton
GitHub Stars
0
Server Listing
DataEdmonton MCP

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation3/5

Tools are mostly distinct, but the set contains several overlapping clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer data questions; polymarket_* tools overlap on betting research; discover_tools and suggest_questions both onboard. Long descriptions reduce confusion, but an agent can still misselect within these families.

Naming Consistency4/5

All names use snake_case consistently, with no mixed casing. However, grammatical patterns vary (verb_noun, noun_noun, adjective_noun) and several tools are domain-prefixed, so the pattern is not a strict verb_noun convention throughout.

Tool Count2/5

34 tools is well above the 3–15 sweet spot and includes redundant or experimental entries such as ask_pipeworx_beta alongside ask_pipeworx. The broad scope may justify some tools, but the count is heavy for a cohesive server and will burden an agent navigating the surface.

Completeness3/5

For Edmonton open data, the surface covers discovery, query, and recent records, but lacks a dataset-detail/schema tool and a generic way to invoke the 5,961 tools that discover_tools describes. The broader Pipeworx coverage is broad but not lifecycle-complete, leaving notable gaps.

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
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