Skip to main content
Glama

words

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. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context about the output: '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.' This explains return format and direct callability, going beyond the structured annotations.

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 concise sentences with front-loaded core purpose: 'Find tools by describing the data or task.' Each sentence contributes distinct information (what, when, return format), with no redundancy or filler.

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?

As a discovery tool with no output schema, the description covers all essential aspects: purpose, when to use, return value (top-N tools with schemas), and note that results are directly callable. Given the moderate complexity and rich annotations, this is fully 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?

Input schema covers 100% of parameters with descriptions, including the main 'query' field and all aliases. The description only mentions 'top-N' which is already detailed in the limit parameter ('default 20, max 50'). Thus, the description adds little value beyond the schema, warranting the baseline 3.

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?

Description begins with 'Find tools by describing the data or task', clearly identifying the verb (find) and resource (tools). It distinguishes itself from domain-specific siblings by explicitly positioning itself as a discovery meta-tool ('Call this FIRST when you have many tools available').

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?

Provides clear context: 'Use when you need to browse, search, look up, or discover what tools exist' and instructs to 'Call this FIRST when you have many tools available and want to see the option set'. However, it does not explicitly state when NOT to use it or name alternative discovery/retrieval tools, so it falls short of a 5.

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

All words 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

A3.7/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx_beta is currently identical to ask_pipeworx, and find_related with syn/rhy options duplicates find_synonyms and find_rhymes. The six Polymarket tools and four entity-research tools also have fuzzy boundaries, so agents will struggle to reliably pick the right one.

Naming Consistency2/5

Conventions are mixed: most tools follow verb_noun (ask_, find_, compare_, validate_) but several are bare nouns or noun phrases (entity_profile, recent_alertes, recent_changes) and others are bare verbs (remember, forget, subscribe, unsubscribe). The server name 'words' matches only five of 36 tools, adding further confusion about what to expect here.

Tool Count2/5

36 tools is well into the heavy range, and the set bundles word lookups, a universal data router, six Polymarket tools, memory, subscriptions, and meta-utilities under one server. Many of these would be better split into dedicated, purpose-scoped servers.

Completeness4/5

For the dominant data-research and prediction-market scope, the surface is strong: grounded lookups, deep reseach, entity profiles, compareions, change feeds, claim verification, edge scanners, fill-risk checks, subscriptions, and memory are all covered. Minor gaps exist: taking 'words' literally there is no defintion or spelling tool, and there is no generic open-web search, but as a data-research toolkit it is quite complete.

Resources