Skip to main content
Glama
Sign In
trendforge-mcp

trendforge-mcp

by flyflyloop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_game

Retrieve a full game breakdown: Demand/Supply/Timing scores, confidence, risk flags, ranking reason, AI video ideas, and 3 related games. Provide a slug to get actionable YouTube content insights.

Instructions

Get the full breakdown for one game: Demand/Supply/Timing scores, confidence, risk flags, a one-line reason it ranks, AI-generated video ideas (title + angle + why-now), and 3 related games. Needs a slug — get it from list_opportunities first, or pass a slug you know.

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": {
      "slug": "<slug>"
    },
    "name": "get_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGame slug, e.g. 'palworld'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so the description carries full burden. It lists exact output fields and notes the input requirement. There are no hidden side effects or unstated behaviors; as a read operation, this is sufficiently transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, information-dense, and front-loaded. Every sentence earns its place: the first lists the output components, the second provides input acquisition guidance. No fluff.

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?

The tool returns a complex breakdown, and the description enumerates all components, so the agent knows what to expect despite no output schema. The single parameter is fully contextualized with usage guidance. This is complete for one-parameter tool.

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 already defines slug with example, but description adds meaning by explaining where to get the slug ('from list_opportunities first') and that a known slug can also be passed. This goes beyond the schema's basic description.

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?

Specific verb 'Get' + resource 'full breakdown for one game' with enumerated components (scores, confidence, risk flags, reason, video ideas, related games). Clearly distinguishes from siblings by indicating it is per-game and requires a slug, contrasting with list_opportunities.

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?

Provides explicit instruction to obtain slug from list_opportunities first, which implies the typical workflow and alternative. Lacks explicit 'when not to use' but the context is clear enough for an agent to select appropriately.

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

Deploy Server

Other Tools