Skip to main content
Glama

エージェント図鑑(医療・介護・保育)

保育・幼児教育施設キーワード検索

search_childcare_facilities

保育施設(認可保育所、認定こども園、幼稚園、小規模保育、認証保育所など)を、施設名または住所のキーワード、都道府県、市区町村、種別で検索します。query、prefecture、city の少なくとも一つが必要です。現在は東京都と大阪市のパイロット版(約6,100件)で、対象地域は順次拡大中です。定員や受入年齢が公表されている施設ではそれも返します。データ出典:自治体公表リスト。

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_childcare_facilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo市区町村名。例: 中央区、千代田区
typeNo施設の種別
limitNo最大件数(既定50、上限200)
queryNo検索キーワード(施設名・住所への部分一致)
prefectureNo都道府県名。例: 東京都、大阪府

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it does disclose the data source (自治体公表リスト), the pilot-only geographic coverage, and the optional return fields (定員, 受入年齢). It omits ordering of results and what happens when zero facilities match, so an agent cannot fully predict the response shape.

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 sentences, front-loaded with purpose followed by the constraint, coverage caveat, and return/source notes; no filler. The constraint sentence could have been merged with the purpose sentence for tighter structure, but nothing is redundant.

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

Completeness3/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 no annotations, so the description must cover the return profile; it names two optional returned fields and the source but not the record shape or count behaviour beyond the limit parameter. The geographic narrowness is well flagged, making the definition usable, though not exhaustive for a tool with five parameters.

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%, so the baseline is 3. The description adds one genuinely valuable constraint not expressible in the schema — the at-least-one-of requirement across query/prefecture/city, which the empty required list does not convey — but adds no clarification on how the enum 'type' interacts with that rule.

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 (検索) plus resource (保育施設) and enumerates the covered facility categories, so the agent knows exactly what corpus is searched. It implicitly separates itself from the nearby-search siblings by emphasizing keyword/prefecture/city filtering, but never names an alternative tool outright.

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 gives an explicit precondition (at least one of query, prefecture, or city) and discloses the geographic pilot scope (東京都 and 大阪市, ~6,100 records) with a note that coverage is expanding, which directly informs when the tool will return nothing useful. It stops short of naming a sibling tool to use when a user wants radius-based lookup.

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