Skip to main content
Glama

sec

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 idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context beyond annotations by explaining the return format: '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 adds context about what the agent receives and that no further lookups are required.

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 description is front-loaded with the core purpose and includes a long but informative list of domains. It contains four sentences, each serving a purpose (purpose, when to use, return behavior, priority guidance). The domain list is slightly verbose but valuable for an agent to understand the tool's coverage.

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 no output schema, the description does a strong job explaining what it returns (tool names, descriptions, full input schemas with examples) and that results are directly callable. It also covers intended usage contexts. Minor gaps include not specifying how results are ranked or whether search is limited to the current toolset, but these are inferable.

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 fully documents all parameters, including aliases and the limit. The description only adds the 'top-N' concept, which is already reflected in the limit parameter's schema description. Thus it meets the baseline, but does not add significant meaning beyond the schema.

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 'Find tools by describing the data or task,' which is a specific verb+resource definition. It clearly distinguishes the tool from sibling tools as the discovery/meta tool, especially with the explicit 'Call this FIRST' guidance.

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?

The description explicitly states when to use it: 'Use when you need to browse, search, look up, or discover what tools exist for...' and provides a comprehensive list of domains. It also instructs to call it first when many tools are available, effectively telling the agent when not to use alternative tools.

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

All sec 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.9/5.0
Disambiguation2/5

The ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded trio are three variants of the same router — and the beta variant is explicitly stated to be identical to the stable one right now, making mis-selection nearly inevitable. The six polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) also have subtly overlapping boundaries where an agent could easily grab the wrong one.

Naming Consistency4/5

Nearly all tools use snake_case with a clear verb_noun or noun_compound shape (get_company_facts, resolve_entity, recent_changes, polymarket_edges). Minor deviations: the bare-verb memory trio (remember/recall/forget), the brand-style ask_pipeworx* naming, and a mix of verb-first vs. entity-first ordering, but the overall pattern is readable and predictable.

Tool Count3/5

34 tools is well above the typical well-scoped range, but the server's actual scope is enormous — a universal structured-data gateway, prediction-market suite, memory system, subscription system, and utility tools. However, the count feels inflated by genuine redundancy: ask_pipeworx_beta currently duplicates ask_pipeworx, and the polymarket cluster could plausibly be consolidated into fewer tools.

Completeness4/5

Each sub-domain has strong lifecycle coverage: entity resolution (resolve_entity, search_companies), company analysis (get_company_facts/filings, entity_profile, recent_changes, compare_entities), full CRUD for both memory and subscriptions, and an exhaustively covered prediction-market domain (research, edges, arb, fill risk, tracking, cross-venue). Minor gaps exist — there's no direct single-filing document fetch tool (search_within implies fetching via the gateway but no explicit getter), and the AI-visibility tools lack historical tracking — but these are workaround-able rather than blocking.

Resources