Skip to main content
Glama

radio

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context beyond this: it returns top-N results with 'names, descriptions, and full input schemas (with curated examples)' and that 'each result is ready to call directly, no second schema lookup needed.' This clarifies the output format and usage pattern without contradicting the 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?

The description is front-loaded with its primary purpose and then lists supported domains—necessary for a discovery tool. It is longer than minimal but each sentence earns its place: supported categories, return format, and usage recommendation are all valuable. The structure is logical and not redundant with schema fields.

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?

There is no output schema, but the description compensates by detailing exactly what is returned: 'top-N most relevant tools with names, descriptions, and full input schemas (with curated examples).' It also explains why to call this first. It omits edge cases like empty results or error behavior, but for a read-only discovery tool with strong annotations, the description is sufficiently complete for an agent to select and invoke it correctly.

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 already documents every parameter, including aliases and the limit. The description adds minimal extra parameter semantics—only the phrase 'top-N' implies the meaning of limit, but the schema already states 'Maximum number of tools to return (default 20, max 50).' Baseline 3 is appropriate when schema does the heavy lifting.

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+resource: 'Find tools by describing the data or task.' It clearly differentiates from siblings by being the meta-tool for discovering other tools, and the explicit list of supported domains (SEC filings, financials, FDA drugs, etc.) leaves no ambiguity about scope.

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?

It gives explicit 'Use when' guidance: '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 (not just one answer).' This effectively tells the agent to use it before directly invoking specific tools, though it doesn't name explicit alternatives or state 'don't use this when you already know the exact tool.'

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

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

Several tools are nearly interchangeable: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, bet_research overlaps heavily with polymarket_edges and polymarket_arbitrage, and ai_visibility_check vs scan_competitor_ai_presence blur together. Despite detailed descriptions, an agent can easily misselect among these overlapping purpose boundaries.

Naming Consistency3/5

Most names follow a readable verb_noun snake_case pattern (list_countries, search_stations, resolve_entity), but bare verbs like remember/recall/forget and inconsistent prefixes (pipeworx_feedback vs ask_pipeworx, bet_research outside the polymarket_* family) break the pattern. The naming is mixed but still navigable.

Tool Count2/5

35 tools is well into the heavy range, and only 4 of them (get_top_stations, list_countries, list_tags, search_stations) pertain to the server's stated 'radio' purpose. The rest form a sprawling research/prediction-market toolkit, making the server feel like multiple unrelated products fused into one.

Completeness3/5

The radio subset covers basic discovery but misses station detail, genre filtering, and stream URLs, an obvious gap for the named domain. The broader Pipeworx/Polymarket suite is expansive with discovery and grounding tools, but remains uneven with no direct per-source browsing and only read-only prediction-market access.

Resources