Skip to main content
Glama

Celestrak

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds valuable context: self-aggregating, derived from CF analytics-engine, no PII, caching details (5min-1h). No contradictions.

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?

Four sentences, each earning its place: first states purpose, second lists use cases, third explains data source and privacy, fourth notes caching. 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?

With only one parameter and no output schema, description fully explains what the tool returns, how it works, and caching behavior. No missing information for an agent to decide on usage.

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 has 100% coverage with enum and description for 'window'. The description adds practical guidance on window selection ('shorter windows surface what's hot; longer show steady-state demand'), going beyond the schema enum labels.

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?

Clearly describes the tool as returning top tools, packs, and call volume over a specified window. Specific verb ('returns') and resource ('Pipeworx trending'). Distinguishes from siblings by focusing on current agent usage trends.

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?

Lists three explicit use cases (discovering hot data sources, confirming canonical tools, aligning with agent needs). Provides context but does not compare directly with sibling tools or state when not to use.

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

All Celestrak 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
Disambiguation2/5

The tool set mixes several distinct domains (satellite orbital data, Pipeworx data routing, prediction-market analysis, memory management, subscriptions), but within the Pipeworx umbrella there is heavy overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying 5,756 tools. An agent could easily misselect between them, especially since ask_pipeworx and ask_pipeworx_beta are described as currently identical.

Naming Consistency3/5

Many tools follow a clear verb_noun pattern (list_subscriptions, create... none, but compare_entities, resolve_entity, generate_llms_txt, scan_dependency, subscribe/unsubscribe, remember/recall/forget), yet the naming is inconsistent across the set: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, get_satellite, get_group, recent_alerts, recent_changes, entity_profile, and deep_research do not share a uniform convention. CamelCase appears in polymarket_arbitrage, polymarket_edges, etc. while most others are snake_case, and the satellite tools (get_satellite, get_group, search_by_name) form a distinct sub-pattern that clashes with the Pipeworx meta-tools.

Tool Count2/5

34 tools is on the heavy side, and the effective surface is bloated: there are three variants of ask_pipeworx, four polymarket_* tools, three satellite-specific tools that are unrelated to the server's apparent core purpose, and several meta/utility tools (remember, recall, forget, pipeworx_feedback, pipeworx_trending, suggest_questions) that could be consolidated or are only tangentially related. The count itself is not extreme, but the scope is muddled: the server claims the name Celestrak (satellite tracking) while the overwhelming majority of tools are for Pipeworx data access and prediction markets, making the tool count feel inappropriate for either purpose.

Completeness3/5

For the Pipeworx data-access domain, the tool set is quite thorough: natural-language routing, grounded answers, deep research, entity profiling, entity comparison, claim verification, semantic search, and tool discovery are all present. However, there are notable gaps: the subscription lifecycle lacks an update/resume mechanism, and the satellite domain (the server's namesake) is severely incomplete — only three lookup tools with no live tracking, no group listing beyond a handful of groups, and no clear lifecycle CRUD. The memory tools (remember/recall/forget) are minimal but complete for their narrow scope.

Resources