Skip to main content
Glama

Geoapify

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.3/5.0
Behavior3/5

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

The description adds rich behavioral context: delivery channels, rate limits (SMS 10/day), webhook signing, and auto-disable after failures. However, annotations indicate idempotentHint=true while the description suggests each call creates a new subscription ('Returns the new subscription id'), creating a contradiction. OpenWorldHint=true is not clarified.

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 well-structured: purpose first, then requirements, types, and delivery details. It is slightly lengthy but every sentence adds value. Front-loaded with key info. Efficient for the complexity involved.

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 no output schema, the description adequately explains the return value (new subscription id). It covers all parameter details, delivery options, and usage constraints. The tool is complex with 3 parameters and nested objects, and the description leaves no significant gaps.

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

Parameters5/5

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

The description extensively enhances the schema's parameter definitions. It provides concrete examples for each type (sec_8k items, polymarket_edge topic, etc.) and explains delivery options in depth (webhook signing, rate limits, verification requirements). Schema coverage is 100%, and the description adds substantial meaning.

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 specifies the return value (new subscription id) and distinguishes from siblings like list_subscriptions and unsubscribe by focusing on creation. Examples of supported types further clarify the scope.

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 explicit context: requires a Pipeworx OAuth account (not anonymous/BYO), lists supported types with examples, and details delivery channels. It lacks explicit when-not-to-use guidance but implies limitations (e.g., cannot persist for anonymous users).

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

All Geoapify 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
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_grounded, entity_profile, compare_entities, and validate_claim, all retrieving entity data. Agents may struggle to choose correctly between them. Likewise, bet_research, polymarket_edges, and polymarket_arbitrage cover similar prediction market territory.

Naming Consistency3/5

All tool names use underscores, but the verb/noun order varies: compare_entities (verb_noun), entity_profile (noun_noun), scan_competitor_ai_presence (verb_noun), bet_research (noun_verb). Some names are overly long (scan_competitor_ai_presence). The pattern is readable but not fully consistent.

Tool Count3/5

With 31 tools, the count is high but not extreme. However, the set covers geospatial, data retrieval, prediction markets, npm scanning, and memory/feedback - too broad for a single server. Many tools feel added without clear justification, making the set feel bloated.

Completeness2/5

The geospatial subset is incomplete (missing elevation, distance matrix, isochrones). The data access tools overlap rather than form a complete API surface (e.g., no entity update/delete). Prediction market tools are numerous but redundant. The server tries to do too much and lacks depth in any area.

Resources