Skip to main content
Glama

N2yo

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. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, and destructive=false. The description adds meaningful behavioral detail: it returns top-N tools with names, descriptions, and full input schemas with curated examples, ready to call directly with no second lookup needed.

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?

The description is three sentences, front-loaded with the core purpose and then adding a domain list and call-first guidance. Every sentence provides useful information, and the structure is easy to scan.

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?

With no output schema, the description compensates by specifying exactly what is returned: tool names, descriptions, full schemas with examples, and direct callability. Combined with strong annotations and clear usage guidance, the description is complete for this meta-tool.

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 coverage is 100%, so the schema documents all 6 parameters including aliases and examples. The description adds little beyond stating the query is a natural language description, so it meets the baseline without adding extra parameter insight.

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 clearly states the tool finds tools by describing data or task, using verbs like browse, search, look up, and discover, and lists specific domains. This distinguishes discover_tools from its research-focused siblings, which are individual data tools.

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?

The description explicitly says to use it when needing to browse/search/discover available tools and to call it FIRST when many tools are available and a set of options is needed. It gives clear context but does not name specific sibling tools to prefer instead.

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

All N2yo 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.8/5.0
Disambiguation2/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates (beta is currently identical), and the five Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) require careful reading to distinguish. Additionally, entity_profile, compare_entities, and recent_changes all handle company data, and ai_visibility_check vs scan_competitor_ai_presence are clearly paired. The detailed descriptions help, but an agent will frequently misselect among these clusters.

Naming Consistency3/5

All names are lowercase with underscores, so the style is internally consistent. However, the pattern is mixed: many use verb_noun (get_positions, list_subscriptions, resolve_entity) but several are noun-first or noun-only (entity_profile, polymarket_edges, pipeworx_trending, bet_research). There's no strong verb/noun convention across the set, making the naming pattern less predictable than it could be.

Tool Count2/5

With 34 tools, the set exceeds the 16–25 'heavy' range and sits in the 'too many' band. The server name suggests a focused satellite-tracking service, yet only 3 tools (get_positions, get_visual_passes, whats_above) serve that purpose; the other 31 cover unrelated domains like data research, prediction markets, memory, and subscriptions. Even as a general-purpose research platform, the count feels bloated and unfocused.

Completeness3/5

The tool surface is broad, covering satellite tracking, data research, prediction markets, subscriptions, and memory, and within each cluster the main operations exist (e.g., subscription lifecycle, edge analysis + fill risk). However, the scattered scope creates gaps: there's no direct raw-data fetch tool (everything goes through ask_pipeworx), no general web search, and the presence of unrelated utilities (generate_llms_txt, scan_dependency) suggests the domain boundaries are unclear. For its stated satellite purpose, the satellite tools are thin (no TLE, no catalog, no detailed orbit info).

Resources