Skip to main content
Glama

Delightful's Game Research Starter Pack

by com.thisisdelightful
OverviewDiscussionsAdmin

search_techniques

44 search techniques for games research, each with a query you can paste, what it surfaces and why it works. Includes local-language strategies for researching the Japanese, Korean and Chinese markets without reading the language. Use this before searching the open web on a games question — these are the queries that reach material a plain search buries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoYour question in your own words, for example "what are Japanese players saying about a launch". Techniques are ranked by how many of its words they mention, so a whole question works better than one keyword.
marketNoTechniques for this market, plus the ones that apply everywhere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / market / enum
      Previous value: -[
-  "US",
-  "Global",
-  "JP",
-  "KR",
-  "Not market specific",
-  "UK",
-  "DE",
-  "BR",
-  "FR",
-  "CN",
-  "MENA",
-  "IT",
-  "SEA",
-  "CA",
-  "Nordics",
-  "IN",
-  "MX",
-  "ES",
-  "TR",
-  "NL",
-  "AU",
-  "PL",
-  "TW",
-  "EU",
-  "LATAM",
-  "Asia",
-  "BE"
-]New value: +[
+  "US",
+  "Global",
+  "JP",
+  "KR",
+  "Not market specific",
+  "UK",
+  "DE",
+  "IN",
+  "BR",
+  "FR",
+  "CN",
+  "MENA",
+  "IT",
+  "SEA",
+  "CA",
+  "Nordics",
+  "MX",
+  "ES",
+  "TR",
+  "NL",
+  "AU",
+  "PL",
+  "TW",
+  "EU",
+  "LATAM",
+  "Asia",
+  "BE"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / market / enum
      Previous value: -[
-  "US",
-  "Global",
-  "JP",
-  "KR",
-  "UK",
-  "Not market specific",
-  "DE",
-  "FR",
-  "CN",
-  "MENA",
-  "IT",
-  "SEA",
-  "CA",
-  "Nordics",
-  "BR",
-  "IN",
-  "MX",
-  "ES",
-  "TR",
-  "NL",
-  "AU",
-  "PL",
-  "TW",
-  "EU",
-  "LATAM",
-  "Asia",
-  "BE"
-]New value: +[
+  "US",
+  "Global",
+  "JP",
+  "KR",
+  "Not market specific",
+  "UK",
+  "DE",
+  "BR",
+  "FR",
+  "CN",
+  "MENA",
+  "IT",
+  "SEA",
+  "CA",
+  "Nordics",
+  "IN",
+  "MX",
+  "ES",
+  "TR",
+  "NL",
+  "AU",
+  "PL",
+  "TW",
+  "EU",
+  "LATAM",
+  "Asia",
+  "BE"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / market / enum
      Previous value: -[
-  "US",
-  "Global",
-  "JP",
-  "KR",
-  "Not market specific",
-  "UK",
-  "DE",
-  "FR",
-  "CN",
-  "MENA",
-  "IT",
-  "SEA",
-  "CA",
-  "Nordics",
-  "BR",
-  "IN",
-  "MX",
-  "ES",
-  "TR",
-  "NL",
-  "AU",
-  "PL",
-  "TW",
-  "EU",
-  "LATAM",
-  "Asia",
-  "BE"
-]New value: +[
+  "US",
+  "Global",
+  "JP",
+  "KR",
+  "UK",
+  "Not market specific",
+  "DE",
+  "FR",
+  "CN",
+  "MENA",
+  "IT",
+  "SEA",
+  "CA",
+  "Nordics",
+  "BR",
+  "IN",
+  "MX",
+  "ES",
+  "TR",
+  "NL",
+  "AU",
+  "PL",
+  "TW",
+  "EU",
+  "LATAM",
+  "Asia",
+  "BE"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / market / enum
      Previous value: -[
-  "US",
-  "Global",
-  "JP",
-  "KR",
-  "Not market specific",
-  "UK",
-  "DE",
-  "FR",
-  "CN",
-  "MENA",
-  "IT",
-  "SEA",
-  "CA",
-  "Nordics",
-  "BR",
-  "IN",
-  "MX",
-  "ES",
-  "TR",
-  "NL",
-  "AU",
-  "PL",
-  "TW",
-  "EU",
-  "LATAM",
-  "Asia"
-]New value: +[
+  "US",
+  "Global",
+  "JP",
+  "KR",
+  "Not market specific",
+  "UK",
+  "DE",
+  "FR",
+  "CN",
+  "MENA",
+  "IT",
+  "SEA",
+  "CA",
+  "Nordics",
+  "BR",
+  "IN",
+  "MX",
+  "ES",
+  "TR",
+  "NL",
+  "AU",
+  "PL",
+  "TW",
+  "EU",
+  "LATAM",
+  "Asia",
+  "BE"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Free text over the technique and how it works."New value: +"Your question in your own words, for example \"what are Japanese players saying about a launch\". Techniques are ranked by how many of its words they mention, so a whole question works better than one keyword."
  6. Changed1 schema field changed
    • changedInput schema / properties / market / enum
      Previous value: -[
-  "US",
-  "Global",
-  "JP",
-  "KR",
-  "UK",
-  "Not market specific",
-  "DE",
-  "FR",
-  "CN",
-  "MENA",
-  "IT",
-  "SEA",
-  "CA",
-  "Nordics",
-  "BR",
-  "IN",
-  "MX",
-  "ES",
-  "TR",
-  "NL",
-  "AU",
-  "PL",
-  "TW",
-  "EU",
-  "LATAM",
-  "Asia"
-]New value: +[
+  "US",
+  "Global",
+  "JP",
+  "KR",
+  "Not market specific",
+  "UK",
+  "DE",
+  "FR",
+  "CN",
+  "MENA",
+  "IT",
+  "SEA",
+  "CA",
+  "Nordics",
+  "BR",
+  "IN",
+  "MX",
+  "ES",
+  "TR",
+  "NL",
+  "AU",
+  "PL",
+  "TW",
+  "EU",
+  "LATAM",
+  "Asia"
+]
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does useful work by revealing that the tool returns techniques rather than search results, and by flagging the local-language strategies for JP/KR/CN markets. But it is silent on result volume (44 items, likely paged or capped), and gives no auth or rate-limit context for a lookup tool.

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?

Three sentences, front-loaded with the concrete payload (44 techniques) and ending on the differentiator. Slight promotional padding in 'the queries that reach material a plain search buries', but every sentence still carries information.

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?

There is no output schema, so the description must explain what comes back, and it does: queries, what they surface, and the rationale. For a zero-required-parameter read tool with fully documented inputs, this is close to complete, missing only scale/pagination expectations.

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 both parameters already document their semantics, including the word-match ranking behavior for 'query' and the enum values for 'market'. The description only loosely implies the market parameter via the local-language sentence, so it adds little beyond the schema; baseline 3 applies.

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?

Names a specific resource (44 search techniques for games research) and states concretely what each entry contains: a pasteable query, what it surfaces, and why it works. The verb 'search' plus the technique inventory makes the tool's identity clear, though it never distinguishes itself from siblings like search_sources or get_source.

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?

'Use this before searching the open web on a games question' gives a clear usage trigger and sequencing instruction. It does not, however, contrast itself against the sibling tools (get_landscape, get_market, search_sources) that an agent would also consider for a games question.

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

All Delightful's Game Research Starter Pack 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