Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.6/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 burden, and it does disclose the return shape: top-N most relevant tools with names, descriptions, and full input schemas plus curated examples, ready to call directly. That is genuinely useful behavioral context, but the text is truncated mid-sentence ("...no") and says nothing about cost, auth, or ranking/pagination semantics beyond the schema's limit field.

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 and efficient, but the description degenerates into a long run-on domain enumeration and ends with a truncated fragment ("...no"), which is both wasted space and a structural defect. The list has some routing value, yet it is not organized or bounded.

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, and the description compensates by explaining exactly what comes back (names, descriptions, full input schemas with examples, directly callable). Parameters are fully covered by the schema. The only gaps are the truncated tail and the unstated scope relative to sibling discovery 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?

Schema description coverage is 100% — every parameter including the six aliases (q, task, search, description) and limit (default 20, max 50) is documented in the schema with an example query. The description adds no parameter-level meaning beyond that, so the baseline of 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 ("Find tools") and resource (tools) plus the mechanism ("by describing the data or task"), and the domain enumeration (SEC filings, FDA drugs, FRED, ATTOM, etc.) makes clear this is a cross-domain discovery index. It does not, however, say how it relates to the identically-named `*__discover_tools` siblings — whether it searches a global catalog or is scoped to numverify-adjacent data — which leaves a residual ambiguity.

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 an explicit trigger condition with concrete example domains. It stops short of any when-not guidance or naming an alternative path (e.g., the per-provider discover_tools siblings), so it is clear context without exclusions.

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.