Skip to main content
Glama

PlugRail JP Recall

search_recalls

Read-onlyIdempotent

消費者庁リコール情報サイトをキーワード+カテゴリで検索します。検索語は日本語推奨(英語の代表語は日本語に読み替えます。例: 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件までを確認」と明記します。category は文字列 "0"〜"13"(数値の 0 は不可)。posted_since/posted_until は YYYY-MM-DD の実在日のみ(例: "2026-09-01"。2026/09/01・20260901 は不可)。

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

Input Schema

NameRequiredDescriptionDefault
limitNo取得件数 1〜15(省略時は15)。例: 15
cursorNo前回応答の nextCursor(透過・省略可)。
keywordNo検索キーワード(30文字以内)。例: "サーキュレーター"
categoryNoカテゴリ 0-13(0=すべて)。例: "0"。1-13 指定時は keyword 空でも可
posted_sinceNo掲載日の下限(YYYY-MM-DD・両端含む。省略=下限なし)。例: "2026-09-01"
posted_untilNo掲載日の上限(YYYY-MM-DD・両端含む。省略=上限なし)。例: "2026-09-30"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • 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"
  2. Changed2 schema fields changed
    • 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"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/openWorld/idempotent) to disclose non-obvious behavior: kana/full-width/English transliteration is reported back in summary, date filtering walks up to 5 upstream pages (75 items) newest-first, and truncation is flagged in summary. It also defines total_count/range/nextCursor as logical positions in limit units, which an agent could not infer otherwise.

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 purpose, then keyword semantics, then filtering and cursor behavior, with no filler sentences. It is dense and slightly run-on in the middle, and the inline JSON input example partly duplicates examples already present per-parameter in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, annotation-covered search tool with no output schema, the description covers what matters: matching behavior, filter scan cap, pagination model, and type/format constraints. An agent has enough to call it correctly and interpret the response without guessing.

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 3 is the baseline, but the description adds real meaning: category must be the string "0"-"13" (numeric 0 rejected, correcting the anyOf string|number schema), dates must be real YYYY-MM-DD with no slashes or compact form, and keyword accepts JAN/model numbers. Cursor paging semantics are also explained rather than only described.

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: search the 消費者庁リコール情報サイト by keyword + category. It is clearly a search/list tool, which implicitly separates it from the detail-fetching sibling, but it never names or contrasts with that sibling explicitly, so it stops just short of 5.

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 concrete usage context: use Japanese keywords with English terms read as Japanese equivalents, pass JAN/model numbers directly to keyword, and category 1-13 works without a keyword. It does not state when to prefer this over alternatives or when to stop searching, so the routing guidance is helpful but not exclusive.

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.