Skip to main content
Glama

Opensea

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by disclosing that results are 'top-N most relevant tools 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 goes beyond annotations to explain output structure and readiness.

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?

Four well-structured sentences, each contributing unique information. The first sentence states the purpose, the second lists example domains, the third explains the return value and readiness, the fourth gives usage advice. No redundancy or fluff.

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?

Despite no output schema, the description fully explains what the tool returns (tool names, descriptions, full input schemas with examples) and how to use it. It covers key usage context (first call for discovery) and the scope of coverage (numerous data domains). No gaps remain given the tool's simple nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all 6 parameters described. Description reinforces the 'query' parameter purpose with examples and clarifies 'limit' meaning indirectly ('top-N'). It also adds context that results include 'curated examples' and schemas, which enriches understanding beyond the raw 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?

Description clearly states 'Find tools by describing the data or task' and provides numerous examples of search domains (SEC filings, FDA drugs, etc.). It distinguishes itself from sibling tools by positioning itself as a discovery tool for browsing the available toolset, not for direct answer generation.

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 advises 'Call this FIRST when you have many tools available and want to see the option set (not just one answer)'. This provides clear when-to-use guidance. Lacks explicit when-not-to-use statements or alternative tool names, but the context is sufficient.

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

All Opensea 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.6/5.0
Disambiguation2/5

Tools cluster into overlapping groups: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates distinguished only by mode; bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. The five OpenSea read tools are distinct, but they are buried among several unrelated domains, making misselection likely.

Naming Consistency4/5

Names are overwhelmingly snake_case with a verb_noun structure (get_collection, list_owned_nfts, validate_claim, create nothing but still remember/unsubscribe). Pipelined families like ask_pipeworx_* and polymarket_* are consistent, with only minor deviations such as pipworx_trending or bet_research not following a clear verb-object pattern.

Tool Count2/5

36 tools is too many for a coherent server, and the count is inflated by at least four unrelated domains: OpenSea NFT reads, Pipeworx data lookup/research, Polymarket betting, and memory/subscription utilities. Only five tools actually relate to the server's stated OpenSea purpose, so the surface is heavily bloated with off-scope functionality.

Completeness2/5

The OpenSea-relevant tools cover basic read operations—collections, stats, single NFT, collection NFTs, and owned NFTs—but omit search, events, offers/listings, order book data, and account/contract details. The many unrelated Pipeworx tools do not fill these gaps, so an agent needing real marketplace behavior would hit dead ends.

Resources