Skip to main content
Glama

Regrid

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description extensively discloses behavioral traits beyond annotations: authentication requirements (Pipeworx OAuth, not anonymous/BYO), delivery channel constraints (SMS cap, phone verification), webhook signing secret returned once, auto-disable after 10 consecutive failures, and type-specific parameter details. No contradiction with annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=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?

The description is appropriately sized given the tool's complexity. It is front-loaded with the core purpose, then organized into clear sections: subscription types, delivery channels, and constraints. Every sentence earns its place without redundancy.

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?

Considering the tool's complexity (3 parameters, nested objects, no output schema), the description is remarkably complete. It covers all subscription types, parameter formats, delivery options, authentication requirements, and behavioral quirks. No gaps are apparent.

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?

Schema coverage is 100%, but the description goes far beyond—providing concrete examples for each subscription type, explaining item codes for sec_8k, delivery channel details, and validation constraints. This adds significant meaning that helps the agent construct correct parameter values.

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 creates a proactive monitoring subscription to a live-data event stream and returns the new subscription id. It uses specific verbs and resources, and its purpose is distinct from siblings like list_subscriptions, unsubscribe, and recent_alerts, even without explicit contrast.

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 clear context for when to use the tool (setting up monitoring subscriptions) and includes important prerequisites like requiring a Pipeworx OAuth account. However, it does not explicitly exclude alternative tools or state when not to use it.

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

All Regrid 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

Most tools have detailed guidance, but several sets blur together: ask_pipeworx_beta is currently identical to ask_pipeworx, polymarket_edges and polymarket_arbitrage both scan for opportunities, and discover_tools/suggest_questions both serve discovery. The descriptions are strong enough to prevent frequent misselection, but the boundaries are not always crisp.

Naming Consistency3/5

Names are consistently snake_case, but the stylistic pattern is mixed: verb_noun names like generate_llms_txt and list_subscriptions sit alongside bare verbs like remember/forget and noun-phrase names like entity_profile, recent_alerts, and polymarket_arbitrage. Prefixes like polymarket_*, pipeworx_*, and regrid_parcel_* add some order, but the set is not uniform.

Tool Count2/5

33 tools is well above the point where a tool set remains easy to navigate, and several tools are near-duplicates or wrappers: ask_pipeworx_beta duplicates ask_pipeworx, scan_competitor_ai_presence is a wrapper around ai_visibility_check, and the prediction-market scanners overlap. The broad domain explains some of the bulk, but the surface still feels overweight.

Completeness3/5

The server covers a wide range of workflows: lookup, deep research, claim validation, entity profiles, comparisons, subscriptions, memory, prediction-market analysis, and parcel lookup. However, the Regrid parcel side is thin with only address and point lookup, and there is no direct tool for parcel-ID/owner/sales/tax queries. These are real gaps, though the universal router helps agents work around them.

Resources