Skip to main content
Glama

holidays

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

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

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description goes beyond by detailing the return format (top-N tools with names, descriptions, and full input schemas ready to call) and the meta-guidance to use it first. This adds valuable behavioral context beyond the annotations.

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 core purpose ('Find tools by describing the data or task') and includes a long but useful enumeration of domains. Each sentence contributes value, though the domain list is somewhat lengthy—still acceptable for setting expectations.

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?

There is no output schema, but the description fully explains the return value: top-N relevant tools with names, descriptions, and full input schemas ready to call. It also covers usage context and the limit parameter implicitly via 'top-N'. For a moderate-complexity tool, this is complete.

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?

Schema description coverage is 100%, with all six parameters (including aliases) documented. The description does not add substantial meaning beyond the schema—it simply reinforces that query is a natural language description. Baseline 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?

The description uses the specific verb 'Find' with the resource 'tools' and clearly states the tool's role as a discovery mechanism. It distinguishes itself from siblings by framing itself as the first step when many tools are available, which is unique among the sibling list.

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?

It explicitly states 'Use when you need to browse, search, look up, or discover what tools exist' and instructs to 'Call this FIRST' when the agent wants to see the option set. This provides clear context for when to use it, though it does not explicitly name alternatives or when not to use it.

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

All holidays 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
Disambiguation1/5

Multiple tools serve near-identical purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical today, ask_pipeworx_grounded and deep_research overlap heavily, and bet_research/polymarket_edges/polymarket_arbitrage all scan prediction-market opportunities. An agent reading these names and descriptions cannot reliably pick one tool without reading very long descriptions.

Naming Consistency2/5

The names are all lower_snake_case, but the naming style is not consistent across the server: verb_noun (get_holidays, validate_claim), bare noun phrases (next_holidays, entity_profile, bet_research), is/are predicates (is_today_holiday), and separate pipeworx/polymarket prefixed groups. There are recognizable subgroups, but no coherent naming convention unifies the full tool surface.

Tool Count2/5

34 tools is over the healthy range and the majority have nothing to do with holidays; they belong to a broader Pipeworx data, prediction-market, and subscription platform. The holiday-specific surface is only three tools buried inside a much larger, unrelated toolkit, making the server feel overloaded and mislabelled.

Completeness4/5

For the actual holiday domain the core read workflows are covered: all public holidays by country/year, today's holiday status, and upcoming holidays. A small gap is the lack of a supported-country/region listing or date-range filtering, but these are easily worked around because get_holidays returns the full year set.

Resources