Skip to main content
Glama

Pangaea

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

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses meaningful behavior: results include full input schemas with curated examples and are 'ready to call directly, no second schema lookup needed.' This adds substantial context about the return format and eliminates ambiguity about the output experience.

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 well-structured and front-loaded: purpose first, then usage, domain list, return behavior, and usage guidance. Every section contributes value, though the synonym cluster 'browse, search, look up, or discover' is slightly redundant and the domain list, while useful, adds length.

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?

Given the absence of an output schema, the description compensates by explicitly explaining what is returned (names, descriptions, schemas with examples) and the top-N ranking behavior. Combined with full parameter coverage and safe annotations, the description is complete enough for initial use.

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 aliases (q, task, search, description) and the limit parameter fully described. The description adds no parameter-level meaning beyond what the schema already provides; it only reiterates the high-level 'describing the data or task' concept.

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 'Find tools by describing the data or task' and enumerates specific domains (SEC filings, FDA drugs, weather, etc.), distinguishing it from sibling tools that are data-retrieval focused. It also specifies the output (top-N tools with names, descriptions, and full schemas), making its purpose unmistakable.

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 clear context: 'Use when you need to browse, search, look up, or discover what tools exist' and gives an ordering cue ('Call this FIRST...'). However, it does not explicitly name alternatives or say when not to use it, so it stops short of a 5.

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

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

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and validate_claim both perform claim verification, and polymarket_edges and polymarket_arbitrage both surface trading opportunities. While descriptions are detailed, the boundaries are fuzzy and agents could easily select the wrong tool.

Naming Consistency3/5

Naming mixes verb-first (search, subscribe, recall, validate_claim) with noun-first (dataset, facets, recent, entity_profile) conventions, and some names are just adjectives or nouns. Consistent prefixed groups exist (polymarket_*, ask_pipeworx_*), but the overall style is inconsistent and the server name 'Pangaea' doesn't align with the dominant 'pipeworx' prefix.

Tool Count2/5

36 tools is excessive for a coherent set, especially given the server bundles unrelated domains (earth science, general data research, prediction markets, memory, utilities). Several tools are redundant (e.g., ask_pipeworx_beta duplicates ask_pipeworx), and many are niche (ai_visibility_check, generate_llms_txt, scan_dependency) that don't fit the apparent primary purpose.

Completeness3/5

The PANGAEA dataset surface covers search, retrieval by ID/DOI, recent, and facets, but lacks export or citation tools. The Pipeworx research tools are broad, but prediction market access has no simple market-price query (only analysis-oriented tools), and there are notable gaps in lifecycle coverage for some subdomains.

Resources