Skip to main content
Glama

Data La

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

DataLA MCP — Los Angeles open data (data.lacity.org, 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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-data-la
GitHub Stars
0
Server Listing
mcp-data-la

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

The four question-answering routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) form an ambiguous cluster — beta is explicitly identical to ask_pipeworx right now and grounded/deep_research are differentiated mainly by prose. Similarly discover_tools, suggest_questions, and pipeworx_trending all answer 'what can I ask / what exists', and compare_entities/entity_profile/recent_changes/bet_research overlap on entity lookups. Descriptions are unusually thorough and do help, but the boundaries require careful reading rather than being self-evident.

Naming Consistency4/5

Nearly everything is snake_case with a predictable verb_noun or noun_noun shape (ask_pipeworx, resolve_entity, entity_profile, la_query, polymarket_edges). Minor deviations exist — bare verbs (remember, recall, forget, subscribe, unsubscribe) and a beta/grounded suffix convention — but the schema is broadly readable and consistent.

Tool Count2/5

At 34 tools this is heavy for the apparent scope, and several entries are near-duplicates (ask_pipeworx vs beta vs grounded, three Polymarket edge/arbitrage scanners) that inflate the count. A single Q&A router plus a mode flag would collapse four tools into one, so the surface carries more tools than its purpose requires.

Completeness4/5

Coverage is unusually broad and self-consistent: routing, identifier resolution, entity profiling, comparisons, claim validation, memory CRUD, subscription lifecycle (subscribe/list/unsubscribe/recent_alerts), and a full Polymarket analysis suite (edges, arbitrage, fill risk, kalshi spread, tracking) are all present. Gaps are minor — no explicit paging/cursor management and some tools are deliberately single-domain — but no obvious agent workflow dead-ends.

Tool Schema Changelog

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

  1. 1 tool update
    • 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."
  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_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

  • la-legislative

    Rehaan12345
    F
    license
    Not graded
    quality
    C
    maintenance
    A read-only MCP server for querying Los Angeles City legislative data - Council Files, votes, member activity, and Neighborhood Council engagement - through parameterized tools without raw SQL.
    1
    -

  • mcp-data-kcmo

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    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.
    2 npm
    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