Skip to main content
Glama

Blockscout

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.

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, and destructiveHint. The description adds that the tool returns top-N relevant tools with schemas and examples, and that results are ready to call directly. This is useful but does not disclose any additional behavioral traits like rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat long due to listing many example domains, but it is front-loaded with the core purpose. Each sentence adds value, though it could be more concise.

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?

Despite no output schema, the description adequately explains what the tool returns: top-N tools with names, descriptions, and full input schemas with examples. This is sufficient for the agent to understand the return format and use the results directly.

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% with all parameters described. The description mentions the limit parameter and that results are top-N, but adds minimal extra meaning beyond the schema. Baseline is 3.

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 that the tool finds tools by describing a data or task, and provides a long list of example domains (SEC filings, FDA drugs, etc.). It distinguishes itself from sibling tools by advising to call it first to see the option set.

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?

The description explicitly says to use this tool when browsing, searching, or discovering what tools exist, and to call it FIRST when many tools are available. This provides clear guidance on when to use it over alternatives.

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

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

B3.3/5.0
Disambiguation1/5

The tool set includes multiple overlapping tools for predictions (bet_research, polymarket_arbitrage, polymarket_edges, etc.) and data lookups (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and mixes blockchain tools with unrelated services, making it difficult for an agent to select the correct tool.

Naming Consistency1/5

Tool names follow no consistent pattern: some use verb_noun (get_address, list_chains), others are multi-word phrases (ai_visibility_check, compare_entities), and styles mix snake_case and camelCase erratically.

Tool Count2/5

With 39 tools, the surface is bloated for a blockchain explorer. Many tools are unrelated to blockchain, inflating the count well beyond what is necessary for the server's stated purpose.

Completeness1/5

The server is named 'Blockscout' but includes mostly non-blockchain tools, leaving the blockchain domain severely incomplete. Even the blockchain-specific tools miss common operations like event logs or internal transactions.

Resources