Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Check how new or crowded an idea is

validate_idea
Read-onlyIdempotent

Check how much research, patents, and companies already cover a product or research idea. Get match counts, crowdedness, growth, and closest prior work before committing.

Instructions

How much research already covers a product or research idea: matching works, works in the last two years, crowdedness (open, early, active, crowded), growth, who is working on it (researchers, institutions, companies), the closest prior work, related patents, the patent trend and possibly free-to-use patents. For a written assessment, use the idea-validation prompt. Runs the Apify Actor tacps126/innovation-radar on your Apify account (about $0.03 per idea; spend per call is capped at $0.5).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ideas": "<ideas>"
    },
    "name": "validate_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideasYesIdeas in plain words, e.g. "a window that generates solar power with perovskite tandem cells".
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive. The description adds genuinely new behavioral facts: it runs a specific Apify Actor on the caller's own account and incurs per-idea cost with a $0.5 per-call cap. It stops short of disclosing expected runtime or what happens on partial Actor failure, which is the remaining relevant gap for an external paid run.

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 metric list is front-loaded and every element corresponds to an actual return field, but the first sentence is a sprawling run-on of twelve comma-separated items. Cost and Actor details sit sensibly at the end, so structure is sound even if the opening could be tightened.

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?

With an output schema present, the enumerated return topics are belt-and-braces rather than required, but cost, account dependency, and the prompt alternative are the missing pieces an agent would otherwise have to guess. Coverage is strong for a two-parameter read tool; only latency and error behavior are left implicit.

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% and the 'ideas' array is documented with its own plain-language example, so the description's restatement of ideas adds little. The 'extra_input' advanced passthrough parameter is never mentioned, so the description does not compensate where the schema is thin on merging semantics beyond 'merged over the defaults'.

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?

States a specific measurement task (how much research covers an idea) and enumerates the concrete outputs: matching works, two-year window, crowdedness states, growth, who is working on it, prior work, patents. This is far more specific than the vague title and clearly separates it from generic search siblings like search_research or search_startup_funding.

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?

Names one explicit alternative route — 'For a written assessment, use the idea-validation prompt' — and gives cost context ($0.03/idea, $0.5 cap) that informs whether to call it for many ideas at once. It does not, however, say when to prefer a sibling like search_research over this tool, so the discrimination guidance is only partial.

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