Skip to main content
Glama

Remoteok

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

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description goes beyond by explaining the data source (CF analytics-engine), that no PII is used, and the caching window (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?

Three sentences, each purposeful: output overview, use cases, transparency details. No redundant or vague language.

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?

Despite having no output schema, the description fully explains what is returned (top tools, top packs, total call volume). Caching behavior is disclosed. For a simple read-only tool with one optional parameter, this is complete.

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% for the single parameter. The description adds semantic value by explaining that shorter windows surface current hotness and longer windows show steady-state demand.

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 opens with a clear statement of what the tool returns ('top tools, top packs, and total call volume') and specifies the context ('What other AI agents are calling on Pipeworx right now'). This distinguishes it from sibling tools like discover_tools or search_within.

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?

Three explicit use cases are listed (discovering hot data sources, confirming canonical choice, aligning use case). While it doesn't explicitly state when not to use it, the context is clear enough for an agent to decide.

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

All Remoteok 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

Several tool clusters have fuzzy boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions through the same routing layer, while polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all address prediction-market edges. Even with detailed descriptions, an agent can easily select the wrong variant.

Naming Consistency3/5

Names are uniformly lowercase snake_case and many follow a verb_noun pattern (list_jobs, search_jobs, resolve_entity, validate_claim), but there are numerous noun-first and adjective-first exceptions (entity_profile, recent_alerts, pipeworx_trending, polymarket_arbitrage) plus bare verbs (remember, forget, recall, subscribe). The pattern is readable but not consistently applied.

Tool Count2/5

34 tools is well above the well-scoped range, and the vast majority are not about the server's RemoteOK namesake. The set appears to merge several distinct domains (Pipeworx data research, Polymarket betting, RemoteOK jobs, memory utilities) into one oversized surface, making it feel more like a bundled platform than a focused server.

Completeness4/5

For the dominant Pipeworx/data-research theme, coverage is strong: question answering, grounded verification, entity profiles, comparisons, change feeds, discovery, memory, subscriptions, and citation-based research are all present. The RemoteOK job subset covers list/search/get without obvious dead ends. Minor gaps exist (no direct citation-URI fetcher, no job alert subscriptions), but agents can work around them.

Resources