Skip to main content
Glama

ゲーム需要・供給の週次比較

get_game_trends
Read-onlyIdempotent

ゲーム別の需要順位・供給順位の週次比較。最大4週までさかのぼり、トップ10ランキングを取得。返却は最新週優先で最大10行。gameは日本語名・英語名のあいまい部分一致(大文字小文字・全半角・空白・記号・かな表記を正規化。英字名は4文字以上の語の1文字の追加・削除・置換にも対応)。既定は登録者1万人以下。集計値は取得できる数値のみ返し、欠損は省略。指標や順位の欠損理由はquality.missing_fieldsに集約し、series_indexesで対象行を示す。latest_available_periodが保存済み最新週、is_latest_periodで各行を識別。period_label_onlyは正確な観測日時不明。Steam人数とYouTube再生数は別指標。

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": "get_game_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNo
limitNo
weeksNo
segmentNou10k

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the description rightly spends its space on output behavior: missing metrics are omitted and their reasons aggregated in quality.missing_fields with row pointers in series_indexes, latest_available_period marks the stored newest week, is_latest_period flags rows, and period_label_only signals an unknown observation date. That is meaningful context an agent cannot get from annotations, though the per-row field set is still only partially described.

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

Conciseness3/5

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

The core purpose is front-loaded in the first sentence and no sentence is pure filler. However, it is one dense run-on block that interleaves parameter rules, ranking semantics, and output-field explanations, making it harder to scan than a partitioned structure would be.

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?

With four parameters, no output schema, and a fairly rich return shape, the description does substantial work: it covers ranking comparison, horizon and row limits, fuzzy name matching, missing-data handling, and week-identification fields. It falls short of fully specifying the returned metric fields and what distinguishes Steam player counts from YouTube view counts beyond noting that they are separate metrics.

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 description coverage is 0%, so the description must carry the load, and it largely does: it details game matching (Japanese/English names, fuzzy partial match with case, width, space, symbol and kana normalization, 1-character edit tolerance for English words of 4+ letters), the 4-week `weeks` cap, the 10-row `limit` cap, and the u10k default for `segment`. The gap is that valid `segment` values other than the default are never enumerated, and the caps are stated as return limits rather than parameter semantics.

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 opening sentence names a specific resource and operation: a weekly comparison of per-game demand rank and supply rank, top-10 ranking, up to 4 weeks back, max 10 rows returned newest-week-first. The subject matter (game demand/supply) is clearly distinct from the VTuber/streaming siblings, though no sibling is named explicitly to sharpen the boundary.

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?

Usage is implied rather than stated: the agent can infer this is the tool for comparing game demand vs supply rankings, and hard constraints (max 4 weeks, max 10 rows, default segment under 10k subscribers) are given. There is no explicit when-to-use/when-not-to-use guidance and no pointer to an alternative sibling tool for related queries.

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.

Resources