Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__discover_tools

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "look up FDA drug approvals"
    },
    "name": "ntsb-investigations__discover_tools"
  }
}

Input 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.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and mostly meets it: it discloses that results are ranked top-N, bounded by a limit (documented in schema), and returned with names, descriptions, and full input schemas with curated examples, and that each result is callable directly without a second lookup. That is genuinely useful behavioral context well beyond annotations. The trailing truncation ("...no") leaves a promised caveat unfinished, costing a point.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core instruction is front-loaded in the first sentence, which is good. But the middle is a long comma-run keyword dump of data providers that reads as SEO filler rather than guidance, and the final clause is truncated mid-word, which looks like a packaging defect. Structure is serviceable, efficiency is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does supply the essential return shape (tool names, descriptions, full schemas, directly callable), which is the critical missing piece. What remains thin is the operational envelope: no mention of ranking behavior, empty-result handling, or cost/latency, and the truncated closing sentence leaves an unfinished qualification. Adequate for a discovery tool, but not 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% and every parameter (query, its four aliases, limit with default 20 / max 50) is already documented in the schema, so the baseline of 3 applies. The description adds no natural-language nuance about how to phrase the query or how limit interacts with result quality; it does not compensate beyond the schema because it does not need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: "Find tools by describing the data or task." The domain enumeration (SEC, FDA, FRED, BLS, ATTOM, USPTO, etc.) effectively scopes which slice of the catalog this discover_tools covers, which matters given the many sibling *__discover_tools variants. It stops short of a crisp one-line differentiation and the closing clause is cut off mid-sentence, so it is clear but not airtight.

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

Usage Guidelines3/5

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

"Use when you need to browse, search, look up, or discover what tools exist for: ..." gives an explicit trigger plus the covered subject areas. However, it offers no when-not guidance (e.g., what to do once you already know the tool name, or whether to prefer a direct tool over discovery) and does not name a concrete alternative. Usage is implied more than bounded.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.