Skip to main content
Glama

Game Chronica

題名からソフトを探す

search_titles
Read-onlyIdempotent

ファミコン・スーパーファミコン・ゲームボーイの日本発売ソフトを題名の一部で探し、発売日・発売元・定価を返す。カタカナ/ひらがな、全角/半角、空白や記号の違いは無視する。英題(作品の欧文題)でも一部は当たる。回答では出典として各ソフトの 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": {
      "query": "<query>"
    },
    "name": "search_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返す件数(既定 10、最大 20)
queryYes題名の一部(例:ドラゴンクエスト、まりお、Tetris)
platformNoハードで絞る。famicom=ファミリーコンピュータ(ディスクシステム含む) / sfc=スーパーファミコン / gb=ゲームボーイ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (read-only, idempotent, closed-world), so the description's contribution is the search semantics: normalization rules and partial English-title matching, plus the requirement to cite each title's url as the source. That goes beyond the structured fields. What's missing is any note on result ordering, what happens with zero hits, or the 20-result cap's effect on a broad query.

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?

Four short sentences: scope and return values first, then matching behavior, then the citation requirement. Each sentence carries information and none is filler. The instruction about citing urls is placed last where it may be skimmed, though it's a reasonable closing note about output.

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, and the description compensates by naming the returned fields (release date, publisher, price, url). Combined with the full schema coverage on the three parameters and the annotations covering safety, an agent has enough to invoke it correctly. Result ordering and behavior on empty results are the only remaining gaps.

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%, with limit, query, and platform all documented, including the enum meaning of each platform. The description adds the useful nuance that query matching ignores script, width, and punctuation differences, but nothing beyond that, so the baseline of 3 is the right fit.

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?

The description opens with a specific verb and resource ('日本発売ソフトを題名の一部で探し') and states both the platform scope (Famicom/SFC/Game Boy) and the returned fields (release date, publisher, price). That scope, title-fragment lookup, is clearly distinguishable from the date-oriented siblings releases_in_month and releases_on_date.

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?

It tells the agent the input is a title fragment and spells out matching tolerance (katakana/hiragana, full/half width, spaces and symbols ignored; some English titles match), which sets the expectation for whether a query will succeed. It doesn't explicitly say when not to use it, or that date-based lookups belong to the sibling tools, so it stops short of full routing guidance.

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