Skip to main content
Glama

What Korea Basics covers

get_korea_basics_overview
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Describe Korea Basics and list what it covers: entry and customs rules, places and curated collections, photo sets and live views, visitor statistics, dates, practical travel tools, lodging licence lookup, and what the user can do on the site (open places in map apps, save to My Korea, add dates to a calendar). Pass a section name to list the items in it. Call this when the user asks what this source knows or where to start.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoOptional. "rules", "guides", "tools" and "collections" list the items with their ids; "values" lists the region, theme and tag words the place tools accept; "site" lists what can be done on the site.

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields and the description adds nothing contradicted. What the description does add beyond the annotations is the behavioural fact that the parameter acts as a filter over sections, and that "values" exposes the accepted region/theme/tag vocabulary — useful orientation. It does not describe response shape (no output schema exists), but for a single-parameter read-only overview this is a modest gap rather than a serious one.

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?

Front-loaded and well ordered: purpose, then covered areas, then the parameter behaviour, then the invocation trigger as the closing sentence. It is dense — the coverage enumeration runs long and largely mirrors the enum values — and the leading Korean label adds little for a calling agent, but no sentence is a pure restatement of the name.

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?

For a zero-required-parameter, read-only orientation tool with a fully described enum and no output schema, the description supplies everything needed to call it correctly and to know what a call will surface. The only omission is that it never routes the agent onward to the concrete sibling tools once the overview has been read, which would have closed the loop.

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% and the enum's own description already spells out what each section value returns, so the schema carries the semantics. The description reinforces this with "Pass a section name to list the items in it" and flags that the unparameterised call returns the catalog overview, but adds no syntax or format detail the schema does not already give. Baseline 3 is the correct landing point.

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 uses a specific verb+resource combination ("Describe Korea Basics and list what it covers") and enumerates the covered domains — entry/customs rules, places, collections, photos, statistics, dates, tools, lodging lookup, and site actions. That makes the tool's identity as a meta/overview entry point clear. It stops short of 5 because it never names the sibling lookup tools it sits in front of (search_korea_basics, get_korea_topic, get_korea_place), so the boundary is inferred from "where to start" rather than stated.

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?

Explicit trigger given: "Call this when the user asks what this source knows or where to start." That is a genuine when-to-use rule tied to a user intent, not a generic restatement. It lacks any when-not guidance or a named alternative for actual lookups, which keeps it below 5.

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