Skip to main content
Glama

Openholidays

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

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

Annotations already declare safe read-only behavior. Description adds valuable context: derived from analytics, no PII, caching delays. 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?

Concise, front-loaded with main function and use cases. Every sentence adds value without redundancy.

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 no output schema, description covers return content (top tools, packs, volume), caching behavior, privacy, and window semantics. Fully adequate for a simple tool.

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 covers 100% of parameters with enum and descriptions. Description adds practical usage nuance for window choice (short-term vs steady-state).

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 it returns top tools, top packs, and call volume over configurable windows. Three specific use cases distinguish it from sibling tools.

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?

Use cases are explicitly listed (discovery, confirmation, alignment), providing clear guidance. Lacks explicit exclusions or comparisons to alternatives, but context from siblings helps.

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

All Openholidays 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.8/5.0
Disambiguation2/5

Several tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple Polymarket tools) and many serve unrelated domains, making it hard for an agent to distinguish which tool to use for a given task, especially given the server's holiday theme.

Naming Consistency3/5

Most tool names follow a lowercase_with_underscores pattern, but the prefixes vary (ask_pipeworx, pipeworx_*, polymarket_*, etc.) and some names are less descriptive (e.g., process, run, execute-like vague verbs are absent, but still the naming lacks a unified convention across the broad set.

Tool Count2/5

35 tools is excessive for a server named 'Openholidays'. The vast majority of tools (e.g., SEC filings, Polymarket, npm scanning) are unrelated to holidays, making the tool count feel bloated and unfocused.

Completeness3/5

For the holiday domain, the server includes necessary tools (list_countries, list_subdivisions, public_holidays, school_holidays) and is complete. However, the server's actual scope is far broader, and many unrelated tools are present, which dilutes the completeness for its stated purpose.

Resources