Skip to main content
Glama

Data Ny

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
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: it returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples), and each result is ready to call directly without a second schema lookup. It does not cover auth or rate limits, but given the read-only nature and the explicit output shape, it goes 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each earning its place: the first states the core purpose, the second gives usage context and domain examples, and the third adds return-value specifics and strategic guidance. It is front-loaded, free of fluff, and effectively communicates the tool's value in a compact format.

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?

With no output schema, the description carries the burden of explaining return values, which it does thoroughly: 'names, descriptions, and full input schemas (with curated examples)' and 'each result is ready to call directly.' It covers when to use, what domains it covers, and what the response looks like, making the tool self-explanatory for an AI agent selecting among many sibling tools.

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 input schema covers all parameters with descriptions, including aliases for 'query' and a 'limit' with defaults. The description does not add significant parameter-level detail beyond what the schema provides, though it reinforces that 'query' is a natural language description by repeating the concept. With 100% schema coverage, the baseline is 3, and the description meets but does not exceed it.

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 starts with a specific verb+resource: 'Find tools by describing the data or task.' It clearly distinguishes this tool from siblings by stating it is for discovering which tools exist, not for querying data directly. The explicit 'Call this FIRST' guidance and the list of covered domains further reinforce its unique role.

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?

The description gives clear usage context: 'Use when you need to browse, search, look up, or discover what tools exist for: [list].' It also advises calling this tool FIRST when many tools are available and one wants to see the option set, implying it is not for when a specific tool is already known. However, it does not explicitly name alternative tools or provide a 'when not to use' statement beyond the implication.

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

All Data Ny 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
Disambiguation4/5

Most tools have distinct purposes, but ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim have overlapping functionality in answering factual questions. The detailed descriptions help differentiate them, though some confusion may still arise.

Naming Consistency5/5

All tool names follow a consistent snake_case convention with a verb_noun pattern (e.g., compare_entities, resolve_entity). No mixing of camelCase or other styles, making the naming predictable and uniform.

Tool Count3/5

34 tools is on the higher side, but many are meta-tools (discover, feedback, subscriptions) and some are redundant (ask_pipeworx vs grounded). While the scope is broad, the count could be trimmed for tighter focus.

Completeness4/5

The server covers a wide range of domains (SEC, FDA, FRED, prediction markets, etc.) with strong read and analysis capabilities. Missing update/delete operations and direct trading, but comprehensive for data retrieval and analysis.

Resources