Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does most of it: it states the return shape (top-N relevant tools, each with name, description, and full input schema plus curated examples) and that each result is directly callable. Gaps remain: no statement of ranking/pagination behavior, and the sentence is truncated ('...no'), so a promised condition is never delivered.

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

Conciseness4/5

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

The purpose statement and usage trigger are front-loaded in the first two sentences, and the domain list is dense but earns its space as a relevance signal. The definition is undermined by the dangling final word 'no', which is wasted text and cuts off an otherwise useful clarification.

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?

For a discovery tool with six parameters at full schema coverage and no output schema, the description supplies what matters: intent, covered domains, and the structure of results. It could add whether results are limited to this server's namespace and how relevance ranking works, but an agent has enough to call it correctly.

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 the schema already documents query, its aliases (q, task, search, description), and the limit default/max. The description adds only 'top-N' framing, which is already implied by the limit parameter. Baseline 3 is appropriate.

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', then enumerates the domains it covers (SEC filings, FDA drugs, FRED, Census, BLS, ATTOM, ClinicalTrials, USPTO, weather, news, crypto, stocks). An agent knows exactly what class of operation this is. It does not differentiate itself from the many sibling *__discover_tools entries, so it stops short of a 5.

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?

It gives clear triggering guidance ('Use when you need to browse, search, look up, or discover what tools exist for...') plus a concrete subject-matter list that lets an agent decide relevance quickly. There is no explicit when-not or named alternative, which keeps it below a 5.

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.