Skip to main content
Glama

Crontab

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

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

Annotations already indicate this is a write operation (readOnlyHint false) and idempotent (idempotentHint true). The description adds important auth requirements (Pipeworx OAuth account) and delivery constraints (phone verification, 10/day cap). However, it omits the webhook delivery channel entirely, misleadingly implying only feed/email/sms are available. This is a gap in behavior disclosure.

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 block with three logically ordered sentences: purpose, requirements/types, and delivery channels. Every sentence adds information, and it is front-loaded with the core action. Slightly long but efficient for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (nested params, enums, no output schema), the description covers many essential aspects but leaves notable gaps: webhook delivery is omitted, error handling is not discussed, and the meaning of 'idempotent' behavior is left to annotations. It is adequate but not fully complete for this complex tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds concrete examples and clarifications beyond the schema, such as 'items:["5.02"] = officer change' and the 'topic:"fed"' example for polymarket_edge, plus details on delivery options like feed always being on. This exceeds baseline value.

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 action ('Create a proactive monitoring subscription') and the target resource ('live-data event stream'), and notes it returns the subscription id. This distinguishes it from sibling tools like list_subscriptions, unsubscribe, and recent_alerts.

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 gives clear context: it explains what the subscription does, the required OAuth account, and the supported subscription types. It does not explicitly name alternatives or exclusion criteria, but the context is enough to understand when 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 Crontab 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
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer factual questions with subtle differences that are not immediately clear. Additionally, five polymarket tools cover similar ground (arbitrage, edges, fill risk, spread), making it hard to pick the right one without reading the full descriptions.

Naming Consistency4/5

Tool names are consistently snake_case and mostly follow a verb_noun pattern (e.g., describe_cron, next_runs, validate_claim). Minor deviations exist (bet_research, entity_profile, pipeworx_trending) but the overall style is predictable and readable.

Tool Count2/5

33 tools is well over the high end for a focused server, and the server name 'Crontab' implies a narrow cron utility while most tools are a broad data-research platform. This mismatch makes the count feel bloated and poorly scoped.

Completeness2/5

For a cron server, the set is severely incomplete: only describe_cron and next_runs exist, with no create/delete/update functionality. For the actual data-research domain, it is rich but lacks clear CRUD coverage for many resources, and the inclusion of unrelated cron/memory tools creates dead ends.

Resources