PlugRail JP Recall

search_recalls

消費者庁リコール情報サイトをキーワード＋カテゴリで検索します。検索語は日本語推奨（英語の代表語は日本語に読み替えます。例: stroller→ベビーカー）。かな/全角/英語を読み替えて検索した場合は summary に「〜として検索しました」と明記します。JAN・型番の照会は keyword にそのまま渡せます。入力例: {"keyword": "サーキュレーター", "category": "0", "limit": 15}掲載日の絞り込み posted_since/posted_until（YYYY-MM-DD・両端含む）を指定すると、上流の新しい順に最大5ページ（75件）まで走査して絞り込みます。total_count・range・nextCursor はいずれも limit 単位の論理位置（絞り込みありは絞り込み後、なしは上流順の続き）を示します。上限で打ち切った場合は summary に「上流の先頭75件までを確認」と明記します。

Input Schema

Name	Required	Description
`limit`	No	取得件数 1〜15（省略時は15）。例: 15
`cursor`	No	前回応答の nextCursor（透過・省略可）。
`keyword`	No	検索キーワード（30文字以内）。例: "サーキュレーター"
`category`	No	カテゴリ 0-13（0=すべて）。例: "0"。1-13 指定時は keyword 空でも可
`posted_since`	No	掲載日の下限（YYYY-MM-DD・両端含む。省略＝下限なし）。例: "2026-09-01"
`posted_until`	No	掲載日の上限（YYYY-MM-DD・両端含む。省略＝上限なし）。例: "2026-09-30"

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 6, 2026

addedInput schema / properties / category / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / category / type
```
Removed value: -"string"
```

addedInput schema / properties / cursor / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / cursor / type
```
Removed value: -"string"
```

addedInput schema / properties / keyword / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / keyword / type
```
Removed value: -"string"
```

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / limit / type
```
Removed value: -"number"
```

addedInput schema / properties / posted_since / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / posted_since / type
```
Removed value: -"string"
```

addedInput schema / properties / posted_until / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / posted_until / type
```
Removed value: -"string"
```

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / posted_since

Added value: +{
+  "description": "掲載日の下限（YYYY-MM-DD・両端含む。省略＝下限なし）。例: \"2026-09-01\"",
+  "type": "string"
+}

addedInput schema / properties / posted_until

Added value: +{
+  "description": "掲載日の上限（YYYY-MM-DD・両端含む。省略＝上限なし）。例: \"2026-09-30\"",
+  "type": "string"
+}

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses transliteration feedback in summary ('〜として検索しました'), the 75-item upstream scan cap and its truncation notice, and the logical position semantics of total_count/range/nextCursor under filtering. This is unusually rich behavioral disclosure for a search tool.

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?

Front-loads the purpose, then usage rules, an example, and pagination semantics. Dense but every clause carries operational information; minor overlap with the schema's date-inclusivity wording.

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?

No output schema and no annotations, so the description must cover behavior — and it explains pagination, truncation, and summary-signaling well. Missing only auth/rate-limit context, which is minor for a public read-only search endpoint.

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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: keyword accepts JAN/model numbers verbatim, transliteration is applied, and it clarifies what total_count/range/nextCursor represent relative to limit. Adds value on top of documented params.

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: searches the Consumer Affairs Agency recall site by keyword+category. The sibling get_recall_detail is not named, but the search-vs-detail distinction is unambiguous. Strong but lacks explicit sibling routing.

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?

Gives clear context: Japanese keywords recommended, english terms auto-transliterated, JAN/model numbers can be passed directly to keyword, and a concrete input example. It also bounds date filtering to 75 items / 5 upstream pages. No explicit when-not or sibling alternative, so not a 5.

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

All PlugRail JP Recall tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

search_recalls

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources