Skip to main content
Glama

Game Chronica

指定した月日に発売されたソフト

releases_on_date
Read-onlyIdempotent

ファミコン・スーパーファミコン・ゲームボーイのソフトのうち、指定した月日(年は問わない)に日本で発売されたものを、1983〜2003年の全年分まとめて返す。「今日は何の日(ゲーム)」に使える。各ソフトの url はゲームクロニカの詳細ページ。回答では出典として url を示すこと。

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": {
      "month": "<month>",
      "day": "<day>"
    },
    "name": "releases_on_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes日(1〜31)
monthYes月(1〜12)
platformNoハードで絞る。famicom=ファミリーコンピュータ(ディスクシステム含む) / sfc=スーパーファミコン / gb=ゲームボーイ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real value by disclosing the data range (1983–2003, Japanese releases for the three platforms), that results span all years at once, and that each entry carries a source URL that should be cited — but it says nothing about ordering, result volume, or how non-existent dates behave.

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 tight sentences, front-loaded with the returned resource and scope before the use case and the citation instruction. No filler, though the citation directive is slightly operational rather than definitional.

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 no output schema, the description does the necessary work of saying what comes back (all years combined, per-title URLs) and how to attribute it. It leaves only secondary details unstated, such as sort order and whether duplicate titles across years appear.

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 month and day already carry Japanese descriptions plus range bounds, with the platform enum fully explained. The description only adds that the year is irrelevant and that the three platforms are the universe of results, a marginal gain over the schema.

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?

States a specific verb and resource (returns titles released on a given month/day, any year, Japan, 1983–2003) and names the three covered platforms, so the scope is unambiguous. It does not explicitly contrast itself with siblings such as releases_in_month, so an agent must infer the month+day vs. month distinction from the phrasing alone.

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?

Offers one concrete use case ("今日は何の日(ゲーム)") which implies the intended occasion-driven lookup, but gives no guidance on when to prefer releases_in_month or search_titles, nor any preconditions such as valid month/day pairings. Usage is implied rather than directed.

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