Skip to main content
Glama

Arcgis Roanoke

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?

The description goes far beyond the annotations by disclosing OAuth requirement, persistence rules, phone verification, per-day SMS cap, webhook HMAC signing, delivery of a one-time signing secret, and auto-disable after 10 consecutive failures. These details give the agent a thorough understanding of side effects and operational behavior.

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 a single dense paragraph that covers types, delivery channels, and constraints without excessive verbosity. Every sentence earns its place, though the density could be slightly improved with bullet points or clearer segmentation. It is appropriately sized for the tool's complexity.

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 complexity (5 types, nested delivery object, no output schema), the description comprehensively addresses the subscription creation process: supported types with examples, delivery options, authentication requirements, and how to pull from the persistent feed. No critical usage information is missing.

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 description coverage is 100% and the schema already provides detailed parameter descriptions, including exact JSON shapes and examples. The tool description repeats much of this information without adding new parameter-level semantics, so the baseline of 3 applies due to the high schema coverage.

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 a specific verb and resource: 'Create a proactive monitoring subscription to a live-data event stream' and states it returns a new subscription id. It clearly distinguishes from sibling tools like list_subscriptions and unsubscribe by focusing on the creation action and listing supported types.

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 implies when to use the tool (to set up monitoring) and provides clear constraints, such as requiring a Pipeworx OAuth account and noting that anonymous/BYO cannot persist. It also explains delivery channel options and prerequisites like phone verification. However, it doesn't explicitly discuss alternatives or when not to use it, so it falls short of a 5.

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

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

The tools span vastly different domains (AI visibility, data querying, prediction markets, GIS) with clear descriptions individually, but the set lacks a coherent focus. An agent looking for ArcGIS functionality would be distracted by many unrelated tools, causing confusion in tool selection.

Naming Consistency2/5

Most tool names use snake_case, but there is no consistent verb_noun pattern. Some names are verbs (remember, forget), others are noun phrases (entity_profile, layer_info), and some include underscores inconsistently (generate_llms_txt vs. bet_research). The naming feels arbitrary.

Tool Count1/5

With 33 tools, the count is high, but the vast majority are from Pipeworx and unrelated to the server's stated purpose (Arcgis Roanoke). Only 3-4 tools actually relate to GIS. The tool count is extremely inappropriate for the server's focus.

Completeness1/5

For the implied domain of ArcGIS Roanoke, the tool surface is severely incomplete, lacking CRUD for map layers, spatial queries, or data management. Conversely, the Pipeworx subset is also incomplete on its own (e.g., missing many data sources). The overall surface fails to serve any single domain well.

Resources