Skip to main content
Glama

Arcgis Lakecountyil

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
Behavior5/5

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

Adds substantial behavioral context beyond annotations: OAuth requirement, anonymous/BYO cannot persist, SMS cap (10/day), phone verification, and webhook auto-disable with signing secret. No contradiction with annotations (readOnly=false, destructive=false).

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?

Single dense paragraph, front-loaded with core action, then prerequisites, types, and delivery channels. Every sentence contributes useful information with no wasted words.

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?

Covers core types (sec_8k, polymarket_edge, fred_series) and delivery (feed, email, sms) but omits webhook and two types (patent_grant, clinical_trial) from prose. However, the schema fully describes these, so the description remains fairly complete for a complex tool.

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

Parameters3/5

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

Schema coverage is 100%, and the description largely repeats examples already in the schema (e.g., items:'5.02', topic:'fed'). It adds no new parameter-level semantics beyond what the schema provides, so baseline 3 is appropriate.

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?

Description uses a specific verb+resource: 'Create a proactive monitoring subscription to a live-data event stream.' It also states the return value (subscription id) and clearly differentiates from sibling tools like list_subscriptions/unsubscribe by focusing on creation.

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?

Provides clear context: requires OAuth account, phone verification for SMS, and delivery options. It does not explicitly state when-not-to-use or name alternative creation tools, but does mention pulling the feed via recent_alerts as a consumption alternative.

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

All Arcgis Lakecountyil 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.7/5.0
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, while ask_pipeworx_grounded, deep_research, validate_claim, and entity_profile all perform data lookups with only subtle differences. discover_tools and suggest_questions also serve similar onboarding/exploration roles.

Naming Consistency4/5

Tool names are uniformly snake_case and generally follow a verb_noun or noun_phrase pattern (e.g., ask_pipeworx, query_layer, entity_profile, remember). There is a slight mix between verb-first and noun-first names but no chaotic conventions like camelCase or inconsistent verb tense.

Tool Count2/5

At 34 tools, the count is well above the typical 15-25 range for a coherent server. More critically, the server is named 'Arcgis Lakecountyil' but only 3 tools (search_datasets, layer_info, query_layer) actually relate to ArcGIS; the remaining 31 tools are a broad Pipeworx data platform, creating a severe scope mismatch that makes the count feel excessive and unfocused.

Completeness2/5

For the ArcGIS domain implied by the server name, the surface is barely complete: it offers search, schema inspection, and querying, but no create, update, delete, or management capabilities. Conversely, the Pipeworx side is relatively rich, but that doesn't match the server's stated purpose, leaving the overall set incomplete for its apparent intended use.

Resources