Skip to main content
Glama

Lens Org

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds valuable behavioral details: 'cached 5min-1h depending on window,' 'self-aggregating signal from CF analytics-engine,' and 'no PII.' 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, zero filler. The main output is stated upfront, followed by use cases and operational details. Every sentence adds value.

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?

For a simple read-only tool with one optional parameter and no output schema, the description fully covers purpose, parameters, use cases, caching, and data source. No gaps given the tool's complexity.

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 coverage is 100% with a detailed description for the sole 'window' parameter. The description adds extra semantic guidance: 'Shorter windows surface what's hot right now; longer windows show steady-state demand,' which helps parameter selection beyond the enum values.

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 returns 'top tools, top packs, and total call volume over a recent window.' It distinguishes from sibling tools like 'ask_pipeworx' or 'discover_tools' by focusing on aggregated trending data from other AI agents.

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 three specific use cases: discovering hot data sources, confirming canonical tools, and checking alignment with agent demand. It does not explicitly exclude scenarios or mention alternatives, but the usage context is clear and actionable.

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

All Lens Org 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.7/5.0
Disambiguation2/5

Multiple tool clusters have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three variants of the same router (beta is currently identical), while bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. ai_visibility_check is effectively a single-entity version of scan_competitor_ai_presence, and discover_tools overlaps heavily with suggest_questions.

Naming Consistency3/5

Tool names are uniformly snake_case and descriptive, but the pattern is mixed: verb-first names (ask_pipeworx, compare_entities, search_within) coexist with noun-first names (patent, scholarly, entity_profile), and the Lens.org pairing of patent/patents_search vs scholarly/scholarly_search is structurally inconsistent. Subgroups like pipeworx_* and polymarket_* are internally consistent, keeping the overall set readable.

Tool Count2/5

At 35 tools, this exceeds the 16-25 'heavy' band and bundles at least four distinct domains: Lens.org bibliometrics, Pipeworx data routing, Polymarket trading analysis, and memory/subscription utilities. While many tools serve legitimate purposes, the set feels sprawling and several variants (e.g., the three ask_pipeworx flavors) inflate the count without adding equivalent value.

Completeness4/5

The Pipeworx/Polymarket ecosystem is thoroughly covered with routing, grounded answers, deep research, entity resolution, validation, comparison, monitoring, and memory all present. The Lens.org portion is thin (search + fetch for patents and scholarly works) but covers the core read path; minor gaps exist such as no batch/export operations and no patent-number lookup.

Resources