Skip to main content
Glama

Is this lodging in the licence register

check_korea_lodging_register
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Look up a place to stay in Korea's local licensing records by the address or name on a booking confirmation (the address works best; romanized addresses are matched by their numbers). Returns the matching business with its type, registration month and address, a closure record, or that it could not be confirmed. Not being confirmed does not mean a place is unlicensed: the name may differ or the record may lag.

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": {
      "query": "<query>"
    },
    "name": "check_korea_lodging_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe address or business name as written on the booking, e.g. "22-4 Jahamun-ro 33-gil, Jongno-gu, Seoul" or "Lotte Hotel Seoul".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safety profile is covered elsewhere. The description does add real value beyond them: the possible outcome states (match with type/registration month/address, a closure record, or 'could not be confirmed') and the important caveat that non-confirmation is not proof of being unlicensed because names may differ or records may lag.

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 tight sentences plus a caveat, front-loaded with the lookup action. The '한국 여행 안내·관광 통계 (Korea Basics)' domain prefix is slightly boilerplate but sets context cheaply; nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explaining returns and does so by enumerating the possible results. It also closes the interpretation gap around a negative result, which is the main way an agent could misuse this 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 coverage is 100% and the single parameter already carries an example, so the baseline would be 3. The description earns above that by adding matching behavior: prefer the address, and romanized addresses are matched by their street numbers, which tells the agent how the query string is interpreted.

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?

States a specific verb and resource: 'Look up a place to stay in Korea's local licensing records by the address or name on a booking confirmation.' This clearly separates it from place-search siblings like find_korea_places, since the object is a licensing record rather than a POI.

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?

Gives concrete invocation context (use the address or name as printed on a booking confirmation) and even ranks the inputs: 'the address works best; romanized addresses are matched by their numbers.' It stops short of naming a sibling tool to use instead when the goal is general place discovery, so it is clear but not fully alternative-routing.

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