Skip to main content
Glama

Endoflife

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 provide readOnlyHint, etc. Description adds caching details, data derivation, and no PII, which are useful beyond annotations.

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?

Well-structured with bullet points and separate lines. Front-loaded with result. No redundant information.

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?

Single optional parameter with full description. No output schema but explains returned data. Sufficient for a read-only trending tool.

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 covers the parameter with enum and description. Description adds explanation of window trade-offs, enhancing meaning.

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 states what the tool does: returns top tools, packs, and call volume over a configurable window. Distinguishes from siblings by specific use cases and data source.

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?

Provides three explicit use cases and window guidance. Lacks explicit when-not-to-use, but the use cases cover main scenarios.

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

All Endoflife 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.9/5.0
Disambiguation2/5

The tool set mixes three near-identical ask_pipeworx variants, multiple overlapping prediction-market tools (polymarket_edges, polymarket_arbitrage, bet_research), and three endoflife tools buried among 31 unrelated Pipeworx tools. This makes distinguishing between tools genuinely confusing, especially when several appear to route to the same underlying data.

Naming Consistency3/5

Most names use lowercase snake_case, but the verb-noun pattern is inconsistent: some are verb_noun (list_products, get_product), others noun_noun (polymarket_edges, bet_research), and a few are bare verbs (recall, forget). The style is readable but does not follow a single predictable convention.

Tool Count2/5

With 34 tools, the count is far too high for a server named 'Endoflife'—only three tools actually relate to endoflife.date tracking. The remaining 31 tools belong to a separate Pipeworx platform, making the tool count an extreme over-scoping for the apparent purpose.

Completeness4/5

The endoflife subset is complete: list_products, get_product, and get_cycle cover the full lifecycle of discovering and retrieving release/support timelines with no dead ends. The broader Pipeworx toolkit also appears fairly comprehensive for its own domain, but the mixed set makes it hard to assess a single coherent surface.

Resources