Skip to main content
Glama

One place in detail

get_korea_place
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Details for one place by id or name: its English and Korean name, address, official website, closing days and free-entry or booking conditions (for a given date if one is passed, where the site has them), accessibility facilities, works filmed there, admission figures, and links that open it in the Korea Basics map, Google Maps, Naver Map and Kakao Map. For an airport, station or terminal it lists the entry procedures handled there. Photos and live views are on the linked page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_korea_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe place id from find_korea_places or search_korea_basics, or its name in English or Korean, e.g. "Gyeongbokgung Palace", "경복궁".
dateNoOptional. YYYY-MM-DD, to say whether the place is closed or free on that day.
regionNoOptional. Narrows a name that exists in more than one region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description still adds real context beyond that: results are date-conditional (closing/free-entry status only when a date is passed), airport/station entries include entry procedures, and photos/live views live on the linked page rather than in the response.

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?

Purpose is front-loaded in the first clause, followed by a dense but useful enumeration of returned fields; the final sentence usefully redirects to the linked page. The field list is long but each item is informative rather than filler.

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 no output schema, the description carries the burden of describing returns, and it does so thoroughly, including date-conditional fields and external links. Minor gaps remain: nothing is said about behavior when an id/name is not found or ambiguous, though the optional region parameter hints at that case.

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 coverage is 100%, so all three parameters are already documented, setting the baseline at 3. The description adds only a modest nuance — that date-dependent data depends on whether the site has it ("where the site has them") — without explaining ambiguity handling for names that exist in multiple regions.

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 opens with a specific verb+resource ("Details for one place") and immediately enumerates the returned content: names, address, website, closing days, accessibility, filming locations, admission figures and map links. This makes it clearly distinguishable from the sibling list/search tools that only surface ids.

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?

Usage is only implied: the tool is the detail-fetch counterpart to find_korea_places/search_korea_basics, and the id parameter description references those tools. The description itself never states when to call this instead of get_korea_topic or get_korea_basics_overview, and gives no exclusions.

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