Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Analyse a technology or research field

analyze_field
Read-onlyIdempotent

Analyze technology or research fields from open data to get ranked opportunity scores, momentum, lab-to-market gaps, key players, trends, and patent status for innovation decisions.

Instructions

A landscape of a technology or research field from open research data: an opportunity score (0-100) with its reasons, momentum, lab-to-market gap and geographic concentration; works per year and growth stage; industry participation and the top companies; key researchers, institutions, countries and funders; rising sub-topics, standout recent work, related patents, the worldwide patent filing trend and older European patents that look free to use (expired or lapsed, with legal status). Several fields come back ranked. For written opportunities, use the field-opportunity-analysis prompt. Runs the Apify Actor tacps126/innovation-radar on your Apify account (about $0.03 per field; 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": {
      "fields": "<fields>"
    },
    "name": "analyze_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoYears of history for the trend.
fieldsYesFields or technologies, e.g. "solid state battery", "CRISPR base editing".
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/5.0
Behavior5/5

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

Beyond annotations that mark it read-only, idempotent, open-world, and non-destructive, the description discloses important operational details: it runs the Apify Actor tacps126/innovation-radar on the user's Apify account, costs about $0.03 per field, and caps spend at $0.5 per call. These details materially help an agent understand cost and external dependency behavior.

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 but front-loaded with the core analysis purpose, followed by relevant output categories, cost, and Actor details. It is appropriately sized for a complex analysis tool, though the long list of outputs could be tightened marginally.

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?

Given the output schema exists, the description does not need to fully explain return values, but it still gives a rich overview of what the analysis returns. Annotations cover safety semantics, and the description adds cost, account, and Actor context, leaving no critical gap for invoking the tool correctly.

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 the schema already documents fields, years, and extra_input. The description adds useful context that multiple fields can be supplied and ranked, and that cost is per field, but it does not explain the years parameter or advanced extra_input behavior beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the resource and scope: a landscape analysis of a technology or research field, with a detailed list of outputs such as opportunity score, momentum, researchers, patents, and ranked fields. It does not explicitly differentiate itself from sibling tools like search_research or validate_idea, so it falls short of a 5 despite being highly specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it by describing the analysis it performs and notes that written opportunities should use the field-opportunity-analysis prompt instead. However, it does not name alternative MCP tools or state explicit exclusions such as when to use search_research instead.

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