Skip to main content
Glama

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

周辺の医療機関検索

search_nearby

緯度経度を中心に半径(km)以内の医療機関を近い順に返します。bbox(最小経度,最小緯度,最大経度,最大緯度)を直接指定することもできます(その場合は緯度経度・半径より優先)。

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

Input Schema

NameRequiredDescriptionDefault
bboxNo「最小経度,最小緯度,最大経度,最大緯度」形式の範囲指定
typeNo施設の種別
limitNo最大件数(既定30)。距離の近い順に返します
latitudeNo中心の緯度。例: 35.700
radiusKmNo半径km(既定3、最大50)
longitudeNo中心の経度。例: 139.762

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does disclose real behavior: nearest-first ordering and the fact that bbox overrides latitude, longitude, and radiusKm, which is genuinely useful. It says nothing about permissions, rate limits, pagination, or what happens when neither bbox nor coordinates are supplied, and those gaps matter for a tool whose inputs are all optional.

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?

Two short sentences; the primary radius behavior is front-loaded, and the bbox alternative with its precedence note follows. There is no filler, though the parenthetical syntax detail partly duplicates what the bbox schema description already states.

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?

With six parameters and no output schema, the description should mention what is returned and how results are limited; limit and ordering appear only in the schema. Precedence is covered, but the no-location-parameter case and the shape of the response are not, leaving gaps for a moderately complex search tool.

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 description coverage is 100%, so the baseline is 3, and the description exceeds that baseline by stating the precedence relationship between bbox and the latitude, longitude, and radiusKm parameters. That interaction is semantic and is not expressed in the schema at all, which is exactly the kind of value the description should add.

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 names a specific verb and resource: it returns (返します) medical institutions (医療機関) ordered by proximity within a radius around a lat/lng point. It is clear what the tool does, but it never contrasts itself with the siblings search_facilities or get_facility, so an agent must infer which one to pick.

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?

The description documents both usage modes, radius search and direct bbox specification, and states the precedence rule when both are supplied. It does not say when to prefer this tool over search_facilities or analyze_trade_area, and it does not cover the case where no location parameter is given at all.

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