Skip to main content
Glama

Nasa

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.1/5.0
Behavior4/5

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

The description adds behavioral details beyond the annotations: it specifies returned fields (source, citation_uri, raw payload), explains the 'mark_read' behavior, and mentions the feed is persisted. Annotations already indicate readOnly and idempotent, so the description complements 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two sentences, front-loaded with purpose, and each word adds value. No redundancy, efficient structure.

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 no output schema, the description covers return fields and key behaviors (mark_read, polling). It could mention ordering (most recent) but lacks details on pagination behavior for 'limit'. Still, it is largely complete for a read-only 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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by providing usage examples (e.g., filter by type 'sec_8k', use ISO timestamp for 'since', and set 'mark_read:true') that clarify how parameters are used together.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it pulls fired events from the subscription feed and returns recent alerts. It uses specific verbs like 'pull' and 'returns', and identifies the resource ('subscription feed'). However, it does not explicitly distinguish itself from sibling tools, leaving some ambiguity.

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 usage context: 'Polls work fine' and mentions an alternative endpoint for scripts/dashboards. It implies this tool is appropriate for polling, but does not explicitly state when not to use it or compare with other tools like 'subscribe' or 'list_subscriptions'.

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