Skip to main content
Glama

Arcgis Maricopa

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.4/5.0
Behavior4/5

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

The description discloses important behavioral details beyond annotations: auth requirements (OAuth account, anonymous/BYO cannot persist), rate limits (10/day SMS cap), and delivery semantics (feed always on, email/SMS optional). It doesn't mention webhook (present in schema) or duplicate subscription behavior, but annotations (idempotent) cover idempotency.

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

Conciseness5/5

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

The description is structured with a clear opening sentence, followed by requirements and examples, and then delivery channels. It is dense but every sentence adds value; there is no fluff. The information is front-loaded and well-organized for the complexity of the tool.

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

Completeness4/5

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

The description covers most aspects: purpose, return value, auth requirements, delivery options, and rate limits. It omits two of the five subscription types (patent_grant and clinical_trial) from the list, but the schema enum and parameter descriptions cover them. Since there is no output schema, stating the return value (subscription id) is important and done.

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 description adds meaning beyond the schema by providing examples and explaining the semantics of some types, e.g., 'sec_8k' as '8-K filings matching ticker + item codes' and 'polymarket_edge' as 'Polymarket↔Kalshi cross-venue mispricings'. While schema coverage is 100%, these clarifications help the agent understand the domain.

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 clearly states the tool's purpose: 'Create a proactive monitoring subscription to a live-data event stream.' It uses a specific verb (create) and resource (subscription), and distinguishes it from sibling tools like list_subscriptions and unsubscribe by focusing on the creation aspect. The return value (new subscription id) is also mentioned.

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?

The description provides clear context on when to use the tool (for proactive monitoring) and states prerequisites (Pipeworx OAuth account, verified phone for SMS). It also explains delivery channels, including the always-on feed and optional email/SMS. It doesn't explicitly mention alternatives, but the context with sibling tools makes the use case clear.

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

All Arcgis Maricopa 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

A3.8/5.0
Disambiguation3/5

Many tools have distinct purposes, but there is overlap within the Pipeworx family (ask_pipeworx vs ask_pipeworx_grounded) and Polymarket tools (bet_research, polymarket_edges, etc.). Descriptions are detailed and help differentiate, but the sheer number of tools from different domains can cause an agent to select the wrong one for a given task.

Naming Consistency2/5

Naming is highly inconsistent: some tools follow verb_noun (ask_pipeworx, compare_entities), others are nouns (layer_info, entity_profile), and some have prefixes (pipeworx_trending, polymarket_arbitrage). There is no uniform pattern, making the set feel chaotic.

Tool Count2/5

33 tools is far too many for a server named 'Arcgis Maricopa', which only has 3 GIS-specific tools. The remaining tools are from unrelated domains (polymarket betting, general Pipeworx queries, utilities), making the tool set bloated and unfocused for its stated purpose.

Completeness3/5

For the ArcGIS domain, the set is minimal (only search, schema, and query) and lacks management or analysis tools. However, the broader toolset covers many data domains (finance, drugs, prediction markets), but with gaps like no update/delete operations for the GIS data. The overall coverage is mixed.

Resources