Skip to main content
Glama

Victorian Complaint

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.1/5.0
Behavior4/5

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

While annotations already establish read-only, idempotent, and non-destructive behavior, the description adds valuable context: 'Self-aggregating signal', 'derived from CF analytics-engine', 'no PII', and 'Cached 5min-1h depending on window'. This goes beyond safety to explain data source and freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is front-loaded with the main purpose and uses a numbered list for usage scenarios, which aids scannability. A few details (e.g., 'derived from CF analytics-engine') could be trimmed, but overall every sentence adds value.

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?

With no output schema, the description adequately explains the return types (top tools, packs, call volume). It covers caching, privacy, and usage context, making it sufficiently complete for a simple one-parameter read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides 100% coverage for the single 'window' parameter, including default and the difference between shorter/longer windows. The description merely repeats the enums without adding new meaning, so it stays at the baseline.

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's function: 'Returns the top tools, top packs, and total call volume over a recent window' with specific time ranges. It also distinguishes itself from siblings by focusing on agent call trends, not general tool discovery.

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 'Useful for' section explicitly lists three distinct use cases (spotting hot data sources, confirming canonical tools, aligning use cases with agent needs). This is clear context, though it does not explicitly mention when not to use it or name alternative tools.

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

All Victorian Complaint 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

Multiple tool clusters overlap heavily: three ask_pipeworx variants, five polymarket_* tools, and two AI-visibility tools (ai_visibility_check vs scan_competitor_ai_presence) could easily be misselected. While descriptions are detailed, the boundaries between search/research/bet/compare tools are blurry enough to cause agent confusion.

Naming Consistency4/5

Tool names follow a consistent lowercase snake_case pattern, and most use a verb-first or noun-based descriptive style (ask_pipeworx, bet_research, entity_profile, validate_claim). Minor deviations like deep_research or process_v2 are absent here; the set is largely predictable and readable.

Tool Count2/5

At 32 tools, the server exceeds the 25-tool threshold for heaviness. Many tools are edge-case variants or meta-features (pipeworx_feedback, pipeworx_trending, suggest_questions) that could be consolidated. The server's stated identity as 'Victorian Complaint' also clashes with this scale, making the count feel excessive for the apparent core purpose.

Completeness4/5

The tool set provides broad coverage for data research, entity resolution, comparison, memory, subscriptions, and prediction-market analysis. It supports query, research, discover, validate, and monitor workflows with few dead ends. Minor gaps like a generic 'get_entity' or direct data-writing tools exist, but they are not core to the implied domain.

Resources