Skip to main content
Glama

Pixabay

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and open-world traits. The description adds beyond this: it discloses the data source (CF analytics-engine), the no-PII guarantee, the output tuple shape, and a 5min–1h cache window, giving the agent useful context about staleness and provenance.

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?

Four sentences, each earning its place: purpose, use cases, data provenance/PII, and caching. Slightly longer than an ideal two-sentence description, but there is no filler or redundancy—it is front-loaded and well-structured.

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 tool with one optional parameter and no output schema, the description is fully sufficient. It describes return contents, windows, use cases, and freshness behavior. The agent can confidently decide when and how to invoke it without further clarification.

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 covers the single 'window' parameter 100%, including enum values and semantic explanation (shorter vs. longer windows). The description repeats the valid values but adds no new parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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?

Description clearly identifies the tool as returning trending usage data for Pipeworx (top tools, packs, and total call volume) across a configurable time window. This is specific and distinguishes it from sibling tools like discover_tools (static list) or recent_alerts/recent_changes (event-driven).

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 (hot data sources, canonical tool confirmation, agent alignment check) that give clear context for when to call. It does not name alternative tools for when-not scenarios, but the guidance is concrete and actionable.

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

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

B3.3/5.0
Disambiguation2/5

The tool set contains multiple near-duplicate lookups: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all do the same routing with minor variations, while deep_research and validate_claim also overlap in information retrieval. The two Pixabay search tools are distinct, but the abundance of overlapping data-lookup tools creates real ambiguity.

Naming Consistency2/5

All names use snake_case, but the pattern is inconsistent: some are verb_noun (search_images, validate_claim), others are noun-based (entity_profile, pipeworx_feedback), and variants like ask_pipeworx_beta/grounded introduce ad-hoc suffixing. The naming does not follow a single predictable convention.

Tool Count1/5

With 33 tools, the count is far excessive for a Pixabay server. Only 2 tools (search_images, search_videos) actually relate to Pixabay; the remaining 31 are unrelated Pipeworx data, Polymarket, memory, and subscription tools. The scope is a severe mismatch.

Completeness1/5

For a server named Pixabay, the surface is severely incomplete: only basic image/video search is provided, with no tool for fetching details, downloading, managing collections, or any other lifecycle operation. Meanwhile, the Pipeworx domain is over-covered, but that is irrelevant to the server's stated purpose.

Resources