Skip to main content
Glama

Hackertarget

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

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 second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural 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."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds that it returns top-N tools with full input schemas and curated examples, ready to call directly with no second lookup. This explains the output format and convenience, but doesn't disclose rate limits or edge cases, so a 4 is appropriate.

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?

Three sentences, each serving a distinct role: purpose/timing, output/benefit, and strategic positioning. Front-loaded with the core verb phrase. No fluff or repetition.

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

Completeness5/5

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

Although there is no output schema, the description explicitly describes the return value (top-N tools with names, descriptions, full input schemas, curated examples) and the direct-call benefit. For a low-complexity discovery tool with a single real parameter (query), this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes aliases and examples, so description doesn't need to repeat parameter details. The description enriches the query parameter by listing domain keywords (SEC, FDA, FRED, Census, BLS, ATTOM, etc.), giving the agent a vocabulary of valid query subjects. This adds value beyond the schema's generic 'natural language description'.

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?

The description opens with a specific verb-object pair ('Find tools by describing the data or task') and enumerates many concrete domains (SEC filings, FDA drugs, FRED, Census, BLS, etc.), making the tool's purpose unmistakable. It also differentiates from siblings by positioning itself as the meta-tool for discovering other tools.

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

Usage Guidelines5/5

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

Explicitly states when to use ('when you need to browse, search, look up, or discover what tools exist') and gives a positional rule ('Call this FIRST when you have many tools available and want to see the option set'). It also implies not for single-answer tasks by saying 'not just one answer'.

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

All Hackertarget toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0
Disambiguation3/5

Tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and entity_profile have overlapping purposes, causing potential confusion. However, their descriptions provide some differentiation, so an agent can usually pick the right one with careful reading.

Naming Consistency2/5

Naming is highly inconsistent: mixes verb_noun (ask_pipeworx), noun_verb (reverse_dns), single-word (geoip), and compound phrases (generate_llms_txt). No clear pattern, making it hard for an agent to predict tool names.

Tool Count2/5

44 tools is overwhelmingly high for a single server. The set mixes unrelated domains (network tools, data APIs, memory, prediction markets), suggesting it's a grab bag rather than a focused toolkit.

Completeness2/5

The server lacks a coherent domain, so evaluating completeness is difficult. There are many lookup tools but few for updates or deletes (except memory). The HackerTarget subset is sparse, and the overall surface feels incomplete for any single purpose.

Resources