Skip to main content
Glama

Emergency numbers, emergency rooms, embassies

get_korea_emergency_help
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): For urgent situations in Korea: the emergency and interpretation phone numbers, the emergency rooms nearest a district, neighbourhood or place the user names (Korean name, address, class), or the contact details of the user's embassy where the site has them. The result is complete as given.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOptional. Defaults to the phone numbers, plus emergency rooms when a place is given and the embassy when a country is given.
whereNoOptional. A district, neighbourhood or place name, e.g. "Hongdae", "Jongno-gu", "Haeundae Beach".
countryNoOptional. The user's country, for the embassy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the description only needs to add context. It does add two useful facts: "The result is complete as given" (no pagination or follow-up call) and "where the site has them" (embassy coverage is not guaranteed). That is real but modest added value beyond the annotations.

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 sentences that get to the point and front-load the urgent-situation framing before enumerating outputs. The leading category label "한국 여행 안내·관광 통계 (Korea Basics):" is somewhat冗余 noise for an agent that already has the tool name, but it is short enough not to obscure the purpose.

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?

With zero required parameters, no output schema and a fully documented schema, the description supplies the missing functional picture: what each mode returns and that results are complete. It could still say more about result language or what happens when a place is not found, but nothing essential is missing for correct invocation.

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 all three parameters including the kind enum are already documented in the schema; baseline is 3. The description adds little beyond the schema, and its mention of "Korean name, address, class" describes return fields rather than parameter meaning.

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 resource in concrete terms: emergency/interpretation phone numbers, nearest emergency rooms with Korean name, address and class, and embassy contacts for the user's country. It scopes itself to "urgent situations in Korea," which implicitly separates it from the informational siblings like get_korea_dates or get_korea_visitor_stats, but it never names an alternative tool explicitly.

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 a clear use condition ("For urgent situations in Korea") and, through the kind parameter description, explains the default behavior of combining numbers with rooms or embassy when place/country are supplied. There are no explicit when-not conditions or named alternatives, so it stops short of full routing guidance.

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