Skip to main content
Glama

Diffbot

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.6/5.0
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds value by explaining that results include full input schemas with curated examples and are ready to call directly, which supplements the lack of an output schema.

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 dense and front-loaded with purpose. It uses active voice and lists examples efficiently. Minor improvement could be structuring into bullet points, but it remains concise.

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 the return value: names, descriptions, full schemas with examples, ready to call. This is complete for a discovery tool given its moderate complexity.

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 descriptions for all 6 parameters. The description adds aliases (task, q, description, search) and provides example queries, enhancing understanding beyond the schema alone.

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 the tool finds tools by describing data or task, lists specific domains (SEC filings, financials, etc.), and explains it returns top-N tools with schemas. It distinguishes itself from siblings by saying 'Call this FIRST' for option discovery.

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?

The description explicitly says when to use: 'when you need to browse, search, look up, or discover what tools exist' and advises calling it first. It does not explicitly state when not to use, but the context is clear.

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

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

Multiple research entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and company analysis tools (entity_profile, compare_entities, recent_changes, bet_research) overlap heavily; the five polymarket_* tools also require careful reading to distinguish. Descriptions are detailed, but an agent must parse long disambiguation text to avoid mis-selection.

Naming Consistency2/5

Names mix verb-first (list_subscriptions, validate_claim, remember), noun-first (entity_profile, polymarket_arbitrage), product-prefixed (ask_pipeworx, pipeworx_feedback), and brand-prefixed (diffbot_company, diffbot_extract). No consistent verb_noun pattern across the set; polymarket_* and pipeworx_* prefixes are internally consistent but the overall scheme is chaotic.

Tool Count2/5

33 tools is well beyond the 3-15 sweet spot and in the 'too many' range. Many tools are meta-variants (4 ask_pipeworx flavors, 5 polymarket tools, 2 AI-visibility tools) that could be consolidated.

Completeness3/5

The data-research, prediction-market, memory, and subscription subdomains are each fairly complete at a meta level, with few dead ends. Gaps include no subscription update (delete + recreate required), no explicit memory update, and no direct way to execute an arbitrary discovered Pipeworx tool aside from routing through ask_pipeworx.

Resources