Skip to main content
Glama
yonghwan1106

K-LifeGuard MCP Server

by yonghwan1106

증상 기반 응급실 검색

lifeguard_search_emergency
Read-onlyIdempotent

Scores and recommends the top 5 emergency hospitals near you based on symptoms, real-time bed availability, distance, traffic, and specialized equipment.

Instructions

증상과 현재 위치 기반으로 최적의 응급의료기관을 추천합니다.

실시간 병상 가용성, 거리, 카카오내비 교통 상황, 전문 장비 보유 여부를 복합 스코어링하여 최적의 병원 5곳을 추천합니다.

Args:

  • latitude (number, required): 현재 위치 위도 (예: 37.5665)

  • longitude (number, required): 현재 위치 경도 (예: 126.9780)

  • symptoms (string, required): 증상 설명 (예: "가슴통증", "소아고열", "뇌졸중 의심")

  • radius_km (number, optional): 검색 반경 km (기본값: 10, 범위: 1-50)

  • response_format (string, optional): 출력 형식 "markdown" 또는 "json" (기본값: "markdown")

Returns:

  • 최적 병원 5곳 추천 (순위, 이름, 주소, 연락처, 거리, ETA, 병상, 장비, 점수)

  • 증상 분석 결과 (매칭된 키워드, 권장 진료과, 필요 장비)

  • 스코어링 공식 설명

Examples:

  • "서울 시청 근처에서 가슴통증 환자 발생" → latitude: 37.5665, longitude: 126.9780, symptoms: "가슴통증"

  • "대전에서 소아 고열" → latitude: 36.3504, longitude: 127.3845, symptoms: "소아고열"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes현재 위치 위도 (예: 37.5665)
symptomsYes증상 설명 (예: 가슴통증, 소아고열, 뇌졸중 의심)
longitudeYes현재 위치 경도 (예: 126.9780)
radius_kmNo검색 반경 km (기본값: 10)
response_formatNo출력 형식: 'markdown'은 사람이 읽기 쉬운 형식, 'json'은 프로그래밍 처리용markdown
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which align with the read-only search nature. The description adds behavioral details beyond annotations, such as real-time data integration, scoring formula, and the top 5 result limitation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for Args, Returns, and Examples. It is front-loaded with the purpose and every sentence adds value. There is no fluff.

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?

Given the complexity (5 parameters, no output schema), the description explains the return structure (top 5 hospitals, symptom analysis, scoring explanation) and provides examples. However, it lacks error handling or edge cases (e.g., no hospitals found).

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 baseline is 3. The description adds value with examples (e.g., '가슴통증', '소아고열') and contextualizes parameters like response_format, improving understanding beyond the schema.

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 clearly states the tool recommends optimal emergency medical institutions based on symptoms and current location, using specific criteria. It is distinct from sibling tools like lifeguard_activate_emergency (activation) and lifeguard_find_pharmacy (pharmacy).

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 provides context and examples but does not explicitly state when not to use this tool or compare with siblings. Usage is implied through examples but lacks explicit guidance on alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonghwan1106/k-lifeguard-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server