Skip to main content
Glama

TGGET Niche Research

by io.tgget
OverviewDiscussionsAdmin

Run Signal

run_signal

Adds one check to a finished research and returns the id of the new child research. Use it when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks. A niche scan already runs the usual checks by itself, so this tool is for what is missing. Checks added this way are free: they do not spend researches of the plan.

Checks of a demand research (kind):

  • competitors: who holds the search results for a phrase of the research; pass the phrase in phrase.

  • dynamics: two years of demand history.

  • appstore: App Store apps for the phrase with ratings and freshness.

  • wiki, radar, youtube: public interest and community signals.

  • paid: paid search for the phrase and its strongest candidates: volume, advertiser competition, cost per click.

  • insight: a summary of the findings written by the language model.

  • report: the final niche report, written anew from the current data; needs a finished niche scan.

Checks of a child research:

  • fingerprint: product sites found by a competitors check, with pricing and app links; the parent is that competitors check.

  • reviews: recent App Store reviews of the leaders; the parent is an App Store research.

  • insight also accepts a competitors check as the parent.

The parent must be completed and belong to the account. The check runs in the background: poll get_research with the returned id every 20-30 seconds until status is completed. insight and report are rebuilt at most once an hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the completed research the check is added to, as returned by start_research, get_research or list_research.
kindYesWhich check to add. competitors, dynamics, appstore, wiki, radar, youtube, paid and report need a demand research as the parent; fingerprint a competitors check; reviews an App Store research; insight a demand research or a competitors check.
localeNoOnly for insight and report: language of the text. Defaults to the language the research was started with, then to the language of the account.
phraseNoOnly for competitors: the phrase whose search results are checked, usually one of the candidate phrases of the parent. Defaults to the phrase of the parent. Ignored by the other checks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Id of the completed parent research."New value: +"Id of the completed research the check is added to, as returned by start_research, get_research or list_research."
    • changedInput schema / properties / kind / description
      Previous value: -"Which check to run."New value: +"Which check to add. competitors, dynamics, appstore, wiki, radar, youtube, paid and report need a demand research as the parent; fingerprint a competitors check; reviews an App Store research; insight a demand research or a competitors check."
    • changedInput schema / properties / locale / description
      Previous value: -"For \"insight\" and \"report\": language of the text. Defaults to the language the research was started with, then to the interface language of the account."New value: +"Only for insight and report: language of the text. Defaults to the language the research was started with, then to the language of the account."
    • changedInput schema / properties / phrase / description
      Previous value: -"For \"competitors\": the phrase to check competitors for (one of the parent's candidate phrases). Defaults to the parent phrase."New value: +"Only for competitors: the phrase whose search results are checked, usually one of the candidate phrases of the parent. Defaults to the phrase of the parent. Ignored by the other checks."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that checks run in the background, that the caller must poll get_research every 20-30 seconds until status is completed, that added checks are free, and that insight/report are rebuilt at most once an hour. It also states the parent must be completed and owned by the account.

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?

Purpose and the background/polling contract are front-loaded, and the check catalog is neatly grouped into demand-research vs child-research bullets. The length is largely justified by eleven enum values, though a few lines border on redundant with the schema's own kind description.

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 no-output-schema tool, the description covers the return value (the new child research id), the async completion contract, rate limits, cost, and parent constraints. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description goes further by explaining what each of the eleven kind values actually means and which parent each requires, and clarifies locale/phrase defaults and scope. It adds real semantic value beyond the enum labels.

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 ('Adds one check to a finished research') plus the return value (id of the new child research). An agent can immediately distinguish this from start_research (creates the research) and get_research (polls it).

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?

Explicitly enumerates when to use it ('when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks') and when not to ('a niche scan already runs the usual checks by itself, so this tool is for what is missing'). It also routes to correct parents per check type.

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

All TGGET Niche Research toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources