Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the return payload ('top-N most relevant tools with names, descriptions, and full input schemas (with curated examples)') and that results are directly invocable. The final clause is truncated ('no'), so one behavioral claim is left dangling, but ranking semantics and read-only discovery nature are otherwise conveyed.

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 purpose and return behavior are front-loaded, which is good, but the long enumeration of data domains consumes most of the text and the description terminates mid-clause ('no'), an outright structural defect that leaves a sentence unfinished.

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?

There is no output schema, so the description must explain return values, and it does so concretely (names, descriptions, full input schemas with examples). Only edge behavior such as no-match results and the truncated trailing clause are unstated; for a simple discovery tool with fully documented parameters this is nearly 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%, so query, alias, and limit semantics are already fully documented in the schema. The description only reinforces the natural-language query intent and 'top-N' via its wording; it adds no syntax, tokenization, or ranking hints beyond the structured fields.

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?

States a specific verb and resource ('Find tools by describing the data or task') and immediately scopes it with a concrete list of covered domains (SEC filings, FDA drugs, FRED, BLS, ATTOM, USPTO, etc.). An agent can tell this is a semantic tool-discovery endpoint rather than any domain-specific sibling.

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 explicit triggering conditions and a domain checklist that an agent can pattern-match against a request. It stops short of naming when not to use it or pointing at an alternative, so it is clear context rather than full when/when-not guidance.

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.