Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.7/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose return behavior: top-N results with names, descriptions, and full input schemas plus curated examples, "ready to call directly." That is genuinely useful. It omits result-count semantics when nothing matches, cost/latency, and the sentence visibly truncates at "no", leaving the final claim unfinished.

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?

Wait—this is one front-loaded sentence that leads with the verb then the trigger, with zero throat-clearing.

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?

For a no-output-schema discovery tool, the description should explain what a caller receives and roughly how many; it names the result fields but the final clause is cut off mid-word, so the definition is literally incomplete. Given 6 parameters and alias handling, the schema covers the mechanics well, but the description leaves the caller's post-call expectations only partially resolved.

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%, so query, task, q, search, description, and limit are all documented in the schema itself. The description adds only the general framing "by describing the data or task" and says nothing about the alias set or the limit/default-20 semantics beyond what the schema already states. Baseline 3 applies.

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?

States a specific verb and resource: "Find tools by describing the data or task," then enumerates the coverage areas (SEC filings, FDA, FRED, BLS, ClinicalTrials, USPTO, etc.). It does not, however, distinguish itself from the many sibling *__discover_tools entries, and the enumerated domains sit oddly against the "npi-registry" name, which suggests healthcare-provider data is the owner's scope.

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?

"Use when you need to browse, search, look up, or discover what tools exist for: ..." gives a concrete trigger and an enumerated coverage list an agent can match against a user request. It stops short of stating when NOT to use it (e.g., when the target tool is already known) or naming an alternative.

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.