Skip to main content
Glama

Nasa

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

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

Annotations already indicate idempotentHint=true and readOnlyHint=false. The description adds essential behavioral details: authentication requirement, return value (subscription id), webhook auto-disable after 10 failures, and SMS rate limit (10/day). This enriches understanding beyond the annotations.

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 thorough and well-structured, starting with the core purpose, then prerequisites, then detailed type and delivery information. It is slightly long but every sentence adds value. No 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?

Given the tool's complexity (multiple subscription types and delivery channels) and no output schema, the description covers all critical aspects: creation behavior, authentication, type-specific parameters, delivery options, failure handling, and rate limits. It is fully sufficient for an agent to use the tool correctly.

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 adds substantial value: it provides concrete examples for each type and its params (e.g., sec_8k with items codes, polymarket_edge with topic), and explains delivery channels with constraints (phone verification, webhook signing). This goes far beyond the 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 description clearly states the tool's purpose: 'Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id.' It specifies the resource (subscription to event streams) and the action (create), and distinguishes from siblings like list_subscriptions, unsubscribe, and recent_alerts by focusing on creation.

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 includes important usage context: requires a Pipeworx OAuth account (anonymous and BYO cannot persist), and details delivery channel options. It does not explicitly contrast with sibling tools but the context is sufficient to infer when to use subscribe (for creation) versus list_subscriptions or unsubscribe.

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

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

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), and ask_pipeworx_grounded are three variants of the same router, while bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. The descriptions are detailed, but an agent must read extensively to avoid selecting the wrong tool within each cluster.

Naming Consistency2/5

Naming is a mix of conventions: get_*/search_* for NASA tools, ask_pipeworx_* and polymarket_* family prefixes, plus one-off names like entity_profile, bet_research, deep_research, recent_changes, and scan_dependency. There is no consistent verb_noun or family-wide pattern, making tool selection unpredictable despite each individual name being readable.

Tool Count2/5

36 tools is heavy for a server named Nasa, and only 5 of them are actually NASA-related; the rest form a sprawling general data-research, prediction-market, memory, and subscription toolkit. The count is borderline defensible for a broad data assistant, but it is clearly unjustified under the server's stated NASA identity.

Completeness3/5

As a general data-research assistant the surface is quite complete: discovery, routing, grounded verification, entity profiles, comparisons, memory, subscriptions, and feedback are all covered. As a NASA server, however, there are notable gaps—no EONET events, Earth observation, exoplanet archive, or TLE/mission-specific data—and the large non-NASA tool surface does not fill those gaps.

Resources