Skip to main content
Glama

Game Chronica

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

releases_in_month
Read-onlyIdempotent

ファミコン・スーパーファミコン・ゲームボーイのソフトのうち、指定した年月に日本で発売されたものを発売日順に返す(1983〜2003年)。発売日が年までしか分かっていないソフトは含まない。回答では出典として各ソフトの 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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "releases_in_month"
  }
}

Input Schema

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

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavior: results are ordered by release date, titles with only a year-level release date are silently excluded, and each item carries a url the agent is told to cite. That exclusion rule is exactly the kind of non-obvious filtering behavior annotations cannot convey.

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 compact sentences, purpose and scope front-loaded, followed by the exclusion rule and the citation instruction — nothing is padded. It is unmarked prose rather than structured bullets, but each sentence carries distinct 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?

With no output schema, the description still conveys what comes back (ordered list of titles with a url per item) and what is omitted, which is enough to call the tool and report results correctly. Only the finer return shape (fields beyond url, result size) is left unspecified, which is a minor gap for a read-only listing tool.

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 description coverage is 100%, including the enum mapping for platform, so the schema does the heavy lifting and baseline 3 applies. The description only reinforces that the platform set is limited to Famicom/SFC/Game Boy and that year is bounded to 1983–2003; it adds no format or default details beyond 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?

The description states a specific verb and resource (returns titles released in a given year/month, in release-date order) plus the platform scope and 1983–2003 range, which lets an agent tell this is a month-granularity listing tool. It never names the sibling releases_on_date, so the boundary against the day-granularity variant is left for the agent to infer.

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 by the required year+month framing, but there is no explicit statement of when to prefer this over releases_on_date or search_titles, nor any prerequisite/exclusion guidance about alternatives. It gives the reader enough to know the input shape, but routing between siblings is left to inference.

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