Skip to main content
Glama

Ipqualityscore

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

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

The description provides extensive behavioral context: persistence requirement (OAuth account), delivery channels with constraints (email, sms cap, webhook auto-disable after 10 failures), and return of subscription id. This supplements annotations (non-readonly, non-destructive, idempotent) without contradiction.

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 but effectively front-loads the purpose and then details types and delivery. It could be more structured with bullet points, but every sentence adds value without redundancy.

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?

Given the complexity (3 params, nested objects, multiple types), the description covers core usage, constraints, and return value. No output schema exists, but the description mentions returning subscription id and webhook secret. Minor gaps like error handling are acceptable.

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?

With 100% schema coverage, baseline is 3. The description adds significant value by explaining type-specific parameter structures (e.g., items, topic, series_id) and delivery details including webhook signing and secret return, which is beyond schema descriptions.

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 title and description clearly state the tool creates a proactive monitoring subscription to a live-data event stream and returns a subscription id. It distinguishes itself from siblings like list_subscriptions and unsubscribe by specifying the creation action and required OAuth account.

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 explicitly requires a Pipeworx OAuth account and lists supported subscription types with examples. It provides context for when to use the tool (monitoring live events) but does not explicitly state when not to use it or compare with alternatives like recent_alerts.

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

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

Multiple natural-language query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, discover_tools, suggest_questions) have heavily overlapping purposes, and the descriptions rely on subtle caveats to differentiate them. Similarly, entity_profile vs compare_entities vs recent_changes and ai_visibility_check vs scan_competitor_ai_presence blur boundaries. Only the four check_* tools (email/ip/phone/url) are cleanly distinct.

Naming Consistency2/5

There are some consistent prefixes (check_*, polymarket_*, ask_pipeworx_*, pipeworx_*) but the overall set mixes verb_noun, noun_verb, and standalone adjectival names (deep_research, entity_profile, bet_research, validate_claim, recent_changes). The pattern is readable within families but chaotic across the whole surface, with no unified convention.

Tool Count2/5

35 tools is excessive for a server branded 'Ipqualityscore', especially since only 4 tools actually serve that fraud-checking domain. The rest sprawls into general data research, prediction-market analysis, memory management, subscriptions, and npm dependency scanning — a far larger scope than the name implies. This is a scattershot collection rather than a coherent offering.

Completeness2/5

The IPQS core domain is thin (only email, IP, phone, URL checks) and missing common fraud-screening operations like transaction scoring or domain reputation. Conversely, the Pipeworx side is over-complete with redundant query paths, while unrelated subsystems (memory, subscriptions, feedback) create dead ends that don't serve the server's apparent purpose. The lack of a clear domain makes genuine completeness impossible to assess or claim.

Resources