Skip to main content
Glama

Crypto Fng

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 indicate readOnlyHint=true and idempotentHint=true. The description adds behavioral details beyond annotations: explains the return value includes full schemas and is ready to call directly. No contradiction.

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?

Description is front-loaded with purpose, then lists domains, then explains return value and usage. Every sentence adds value, but it is slightly verbose. Could be more concise without losing clarity.

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?

No output schema, so the description takes on burden of explaining return value. It does so by stating 'top-N most relevant tools with names, descriptions, and full input schemas' and 'ready to call directly'. Complete for a discovery tool with good annotations.

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 baseline is 3. The description mentions aliases but the schema already describes each alias. No significant new semantic 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 clearly states 'Find tools by describing the data or task' with specific verbs and resource. It lists many domains and distinguishes from sibling tools by being the discovery/gateway tool. No ambiguity.

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?

Explicitly says 'Call this FIRST when you have many tools available and want to see the option set' and 'Use when you need to browse, search, look up, or discover what tools exist for: ...'. Provides clear context and when-not-to-use implied.

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

All Crypto Fng 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, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route questions through the same underlying catalog with only subtle differences. The polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) also has fuzzy boundaries. Only the Crypto Fear & Greed tools are clearly distinct.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern, but there are notable deviations: the ask_pipeworx_* family uses object-style names, pipeworx_feedback and polymarket_edges are noun_noun, and current_index vs index_history uses 'index' inconsistently. The polymarket_* family mixes verb and noun styles internally.

Tool Count2/5

33 tools is heavy for a server ostensibly named 'Crypto Fng' — only 2 of the tools relate to that core purpose. The rest constitute a broad generic data-research and prediction-market platform that would be more appropriately scoped as its own server. The count exceeds the comfortable range for an agent to reason over.

Completeness4/5

Within the actual (broad) domain, the surface is fairly complete: discovery (discover_tools, suggest_questions), querying (ask_pipeworx family), grounded verification (validate_claim, ask_pipeworx_grounded), deep research, entity resolution/profile/comparison, memory lifecycle, and subscription lifecycle. The named crypto-sentiment domain is fully covered with current and historical index tools, though the underlying 5,708 pack tools are only reachable indirectly through the router.

Resources