Skip to main content
Glama

Arcgis Princewilliam

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

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context: requires OAuth, feed is always on, phone must be verified, webhook auto-disabled after 10 failures, and webhook signing secret returned only once. It does not contradict 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 lengthy but well-structured: it front-loads the purpose, then covers requirements, subscription types, and delivery channels in a logical order. While it duplicates some schema content, the density of information justifies the length and the organization aids readability.

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?

For a tool with no output schema, the description states the return value and covers auth, all subscription types with examples, delivery options, verification steps, and failure limits. It lacks explicit error-handling information, but given the complexity of the tool, it is reasonably complete.

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?

The schema already provides 100% coverage with detailed descriptions and examples for 'type', 'params', and 'delivery'. The tool description repeats much of this information, offering limited new meaning beyond the schema. The only novel additions are the OAuth requirement and the always-on feed concept, which are more about usage than parameter semantics.

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' which clearly identifies the action and resource. It also specifies the return value ('Returns the new subscription id') and distinguishes itself from sibling tools like list_subscriptions and recent_alerts by focusing on subscription 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?

The description provides strong contextual guidance by listing prerequisites (OAuth account), supported subscription types, and delivery channels. It implicitly differentiates from recent_alerts by noting the always-on feed can be pulled via that tool, but it does not explicitly state when not to use this tool or directly compare with unsubscribe.

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

All Arcgis Princewilliam 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
Disambiguation3/5

The set mixes several overlapping clusters: three ask_pipeworx variants (beta is explicitly identical to stable right now), six Polymarket tools with similar opportunity-scanning purposes, and two AI-visibility tools that duplicate each other. However, the descriptions are detailed enough that an agent can usually pick correctly, so the ambiguity is moderate rather than severe.

Naming Consistency2/5

Tool names follow no single convention — some are verb_noun (query_layer, validate_claim), some noun_noun (entity_profile, layer_info), some company-prefixed clusters (pipeworx_*, polymarket_*), and a few standalone verbs (forget, recall). While snake_case is consistent, the absence of a uniform verb_noun pattern across the set makes it unpredictable.

Tool Count2/5

At 34 tools, the server is oversized for its apparent purpose, and the count is even more problematic because most tools belong to a general Pipeworx/data platform while only 3 serve the 'Arcgis Princewilliam' GIS theme. The set feels like two unrelated servers merged, with many tools earning no clear place in a unified product.

Completeness2/5

The GIS side is a read-only stub (search, schema, and query) with no editing or feature-level retrieval, and the broader Pipeworx side has a notable dead end: tools return pipeworx:// citation URIs but no tool is provided to fetch those resources. The result is a surface that is simultaneously over-built in prediction markets and under-built in its namesake domain.

Resources