Skip to main content
Glama

Nato

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint ensuring safe usage. The description adds valuable behavioral context: returns top-N most relevant tools with full input schemas and curated examples, ready to call directly. No contradictions with annotations.

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?

Single paragraph with efficient sentences. Front-loaded with the primary action. Could be slightly more structured, but no fluff or redundancy.

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?

For a discovery tool with no output schema, the description thoroughly explains what it returns (tool names, descriptions, full input schemas with examples) and that results are callable immediately. It also mentions the top-N relevance ranking. No gaps.

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?

All 6 parameters have schema descriptions (100% coverage), so baseline is 3. The description adds example query phrases (e.g., 'look up FDA drug approvals') and lists many domains, which provides helpful context beyond the schema but does not add meaning to individual parameters.

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 specifies the exact action ('Find tools by describing the data or task') and the resource (tools available). It lists concrete example domains (SEC filings, financials, etc.), making it clear and highly distinguishable from sibling tools, none of which are general discovery 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?

Explicitly states 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This gives clear context for when to use it. Lacks explicit 'when not to use' instructions, but the guidance is strong.

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

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

A4.1/5.0
Disambiguation2/5

Multiple tools blur together: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-variants, and the six polymarket_* tools plus bet_research heavily overlap in purpose. Descriptions are detailed and cross-reference each other, but an agent must read very long definitions to avoid misselection.

Naming Consistency4/5

The set is consistently snake_case with helpful domain prefixes like ask_pipeworx, polymarket_*, and scan_*. Deviations such as deep_research, entity_profile, recent_alerts, and the bare verbs remember/recall/forget break a strict verb_noun pattern but remain predictable.

Tool Count3/5

34 tools is heavy for one server, and several groups could plausibly be consolidated. However, the platform spans data lookup, research, prediction markets, memory, subscriptions, and utilities, so the breadth partially justifies the count.

Completeness5/5

The surface covers lookup, grounded verification, deep research, entity comparison, claim validation, prediction-market analysis, memory CRUD, subscription lifecycle, and discovery. There are no obvious dead ends, and gaps are minor or workaroundable.

Resources