Skip to main content
Glama

Arcgis Pittsburgh

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (which only indicate mutating, idempotent, non-destructive), the description discloses meaningful behavior: requires Pipeworx OAuth (anonymous/BYO cannot persist), phone must be verified, SMS has a 10/day cap, webhook auto-disables after 10 consecutive failures, and the signing secret is returned only once. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and long, but every sentence carries useful detail about auth, types, delivery, and caveats. It front-loads the main purpose and then layers specifics; a bit more structure (e.g., line breaks) would improve scannability, but it is not redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 parameters, nested objects, and no output schema, the description is complete: it explains supported types, parameter shapes, auth requirements, optional vs. always-on delivery, webhook signing, limits, and the fact that the subscription id is returned. An agent can invoke this tool without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers all parameters at 100%, so the baseline is 3. The description adds real value by giving concrete examples (items:['5.02'] = officer change; params:{topic:'fed'}) and reminding that the response includes a one-time webhook secret. It does not fully replace the schema, but enhances it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a proactive monitoring subscription to a live-data event stream' — a specific verb and resource, distinct from sibling tools like list_subscriptions or unsubscribe. It also states the return value (new subscription id), making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when to subscribe: it is for proactive monitoring of live-data streams, with supported subscription types and delivery channels. It does not explicitly name alternatives (e.g., use recent_alerts to view fired events), but the context is sufficient for an agent to choose it over list/unsubscribe tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Arcgis Pittsburgh toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several near-duplicate tool clusters exist: ask_pipeworx, ask_pipeworx_beta (explicitly identical right now), and ask_pipeworx_grounded overlap heavily, as do polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and polymarket_kalshi_spread. The three ArcGIS tools (search_datasets, layer_info, query_layer) are distinct, but their purpose is drowned out by the unrelated Pipeworx data tools.

Naming Consistency2/5

Most names use snake_case, but the pattern is inconsistent: some are verb_noun (ask_pipeworx, search_datasets, resolve_entity), some are noun_noun (layer_info, entity_profile, pipeworx_feedback), and some are adjective_noun (recent_alerts, recent_changes). Verbs are also inconsistent across similar actions (scan_ vs check_ vs compare_, and three different polymarket_ verbs plus a bare bet_research).

Tool Count1/5

34 tools is already heavy, but the server is named Arcgis Pittsburgh and only 3 of the 34 tools relate to Pittsburgh GIS data; the other 31 belong to unrelated domains (Pipeworx data lookup, prediction markets, memory, npm auditing). This is an extreme scope mismatch — the tool count is far too high for the stated purpose and mostly irrelevant noise.

Completeness2/5

For the ArcGIS Pittsburgh domain, the surface has basic read coverage (search datasets, inspect layer schema, query records) but no update/delete/write operations and no geospatial analysis tools, which are significant gaps for a GIS server. The broader tool set is a grab bag of research, prediction-market, and memory features that don't form a coherent lifecycle for any single domain, so completeness cannot be assessed as a unified surface.

Resources