Skip to main content
Glama

tle

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
Behavior4/5

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

The description adds substantial behavioral details beyond the annotations: OAuth requirement (anonymous/BYO cannot persist), always-on feed delivery, SMS verification and 10/day cap, webhook HMAC signing and auto-disable after 10 failures. However, it does not clarify idempotent behavior despite idempotentHint=true; the phrase "new subscription id" is ambiguous as to whether duplicate subscriptions are prevented.

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 dense but efficient, front-loading the purpose and then systematically covering requirements, types, and delivery options. Every sentence adds value, though the length is considerable; the structure is logical and readable.

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?

The description covers purpose, all parameters, behavioral constraints, and the return value (subscription id), including the one-time webhook_secret in the response. It lacks a full return object schema, but for a subscription creation tool, the essential information is provided. Given no output schema, the description adequately covers the return.

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 enriches each parameter with concrete examples (sec_8k items:["5.02"], polymarket_edge topic:"fed") and delivery channel specifics (email, SMS, webhook signing). This goes well beyond the schema's basic descriptions, making parameter usage unambiguous.

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 uses a specific verb and resource, clearly distinguishing it from sibling tools like list_subscriptions, unsubscribe, and recent_alerts. It also states the return value (subscription id), reinforcing the tool's purpose.

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 clearly establishes when to use the tool (proactive monitoring) and includes prerequisites (Pipeworx OAuth account, phone verification for SMS). It does not explicitly contrast with one-off data retrieval tools, though the "proactive monitoring" phrasing implicitly differentiates it. This is clear context without explicit exclusions.

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

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

Most tools have clearly distinct jobs, but ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research are overlapping query/research entry points—and ask_pipeworx_beta is currently identical to ask_pipeworx. Similarly, ai_visibility_check and scan_competitor_ai_presence overlap by composition. The descriptions are detailed enough to choose correctly with care, but the boundaries are not always crisp.

Naming Consistency3/5

All names use lowercase snake_case, which keeps the surface readable, but the naming conventions are mixed: some are imperative verbs (get_tle, list_recent, validate_claim), some are noun phrases (entity_profile, recent_alerts, pipeworx_trending), and several use domain prefixes without a clear verb (polymarket_arbitrage, polymarket_edges). This is still discoverable naming, but it does not follow a consistent verb_noun pattern.

Tool Count2/5

34 tools is well beyond the well-scoped range, and the vast majority belong to a broad Pipeworx research/prediction-market platform rather than the server's apparent 'tle' satellite theme. Only get_tle, list_recent, and search_satellites directly match the server name. It feels like several tool surfaces aggregated into one server rather than one coherent product.

Completeness3/5

For the satellite TLE theme, NORAD lookup, name search, and recent-catalog listing are covered, but orbit propagation, pass prediction, and historical TLE data are missing. For the broader data-research surface, coverage is rich—query, grounded answers, entity resolution, comparison, validation, subscriptions, and memory are all present—so agents have workable paths for most tasks, but the server's mixed scope creates obvious thematic gaps.

Resources