Skip to main content
Glama

Open Notify

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

A5/5.0
Behavior5/5

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

Annotations already declare readOnly=True, idempotent=True, non-destructive. Description adds that it returns top-N most relevant tools with full schemas and curated examples, each call-ready, which goes beyond annotation information.

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?

Description is concise: two main sentences plus a list, front-loaded with purpose, 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?

Given 6 parameters (1 required) and no output schema, description fully covers behavior, return value, and usage context, making it complete for an agent to select and invoke correctly.

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

Parameters5/5

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

Schema coverage is 100% with descriptions. Description adds context about accepting aliases (task, q, description, search) and limit defaults/max, enhancing parameter understanding.

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 finds tools by describing data or task, lists specific domains (SEC filings, financials, etc.), and distinguishes from siblings by noting it returns full input schemas for direct use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Call this FIRST when you have many tools available and want to see the option set (not just one answer),' providing clear when-to-use guidance and implied alternatives (specific tools for specific tasks).

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

All Open Notify 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

The three ask_pipeworx variants are near-identical (the beta is currently an exact copy of the stable router), and ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying source catalog. The six polymarket_* tools also heavily overlap in opportunity detection, though some clusters like memory and subscriptions are clearly separated.

Naming Consistency3/5

The naming is mostly snake_case but mixes conventions: verb_noun (list_subscriptions, resolve_entity), noun-first (entity_profile, bet_research), metadata-style prefixes (pipeworx_trending, polymarket_edges), and bare verbs (remember, recall, forget). It is readable but does not follow one predictable pattern across the set.

Tool Count2/5

33 tools is excessive for a server nominally named Open Notify, and the count is inflated by redundant ask_pipeworx variants and six closely-related Polymarket tools. The broad data-gateway scope could justify a large catalog, but the set feels bloated and unfocused rather than deliberately scaled.

Completeness2/5

For the apparent Open Notify domain, only astros and iss_now fit, and core ISS functionality like pass predictions is missing. The wider data-lookup surface is extensive, but the inclusion of unrelated memory, subscription, npm-scanning, and llms.txt tools means no single domain gets coherent lifecycle coverage.

Resources