Skip to main content
Glama

Find Growth Niches

find_growth_niches

Finds niches an existing business could grow into. Give what the app, site or business does in words, links to its site or its App Store / Google Play apps, or both. TGGET reads the links (maps and social networks are not read), proposes neighbouring products (a new audience, a new task, a feature grown into a product, a new format, a complement), measures their demand in the country and researches the one with the most demand in full. Uses one research of the quota. Poll get_research with the returned id: once status is completed, findings.growth lists the niches (phrase, monthly demand, axis, fit, why, scan_id of the full research or research_url/catalog_url when already measured) and findings.profile what was read about the business. Check another niche with start_research and its phrase in the same country. What the business does stays private; the niches found are researched as usual.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_growth_niches"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoWhat the business does, for whom, how it earns, in your own words, up to 1500 characters. Optional when links are given.
linksNoUp to 3 links: the business site, its App Store or Google Play app.
countryNoCountry to measure demand in, as an ISO 3166-1 alpha-2 code; guessed from the words when absent.
languageNoLanguage the demand is measured in, when the country has several.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint=false annotation it discloses the quota cost ('Uses one research of the quota'), the privacy posture ('What the business does stays private'), the authentication-free reading limits ('maps and social networks are not read'), and the asynchronous polling pattern with the exact status field to watch. It even describes the shape of the eventual findings, which no output schema supplies.

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?

It is dense and slightly run-on in places, but the intent, the inputs, the follow-up loop and the return contents all land in order with no filler sentences. The 'what the business does stays private' note is short and earns its place.

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?

For a four-parameter asynchronous research tool with no output schema, this covers everything an agent needs: how to supply input, the quota cost, the polling loop, the field names to read (findings.growth, findings.profile), the per-niche fields, and the sibling call that continues the work.

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%, so the schema already documents all four parameters. The description still adds real meaning on top: which link types are readable and which are silently unusable, that either text or links must be present, and that country/language drive where demand is measured. This goes past restating the 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?

States a specific verb and resource ('Finds niches an existing business could grow into') and immediately refines it with the five axes of neighbouring products (new audience, new task, feature grown into a product, new format, a complement). An agent can tell this apart from get_research or start_research because the description names the discovery step that precedes them.

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?

It is explicit about the two input paths (describe the business in words, supply links, or both) and about what to do afterwards: poll get_research with the returned id, and use start_research with the phrase in the same country to check a further niche. It excludes reading maps and social networks, and notes the quota cost. What is missing is guidance on when a plain start_research or vip_niches would be the better first call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.