SelectBNBs Verify

Get one government permit record (South Korea)

get_permit_record

Read-onlyIdempotent

Fetch one accommodation permit record from official South Korean government data, by its government management number (e.g. AGCV065100002024000451), optionally with its Korean issuing region, or by registered business name together with the Korean issuing region (e.g. name 'Jobs', region '서울특별시 종로구'). SelectBNBs Verify covers South Korea today; more countries are coming. It takes one of these identifiers and does not read text copied from a listing. Returns one record (status, category, permit date, record page link, citation) or says why no single record could be chosen. Never lists or browses records.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Registered business name (사업장명). Send together with region.
`region`	No	Korean issuing region in Korean, e.g. 서울특별시 종로구. Required with name; optional with management_number, where it picks the local government that issued a shared number.
`country`	Yes	ISO 3166-1 alpha-2 code of the country where the stay is, e.g. KR. Only KR (South Korea) is covered today; other countries return 'not covered yet'.
`management_number`	No	Full government management number, e.g. AGCV065100002024000451. Urban-homestay and hanok numbers (CDFI...) repeat across local governments; send those with region.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`found`	No
`detail`	No
`record`	No	Status, category, permit date, record page link and citation.
`status`	No
`country`	No
`next_step`	No
`check_page`	No
`matched_on`	No
`covered_countries`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedInput schema / properties / management_number / description

Previous value: -"Full government management number, e.g. AGCV065100002024000451. Send this alone. Urban-homestay and hanok numbers (CDFI...) repeat across districts; for those, send name and region instead."New value: +"Full government management number, e.g. AGCV065100002024000451. Urban-homestay and hanok numbers (CDFI...) repeat across local governments; send those with region."

changedInput schema / properties / region / description

Previous value: -"Korean issuing region in Korean, e.g. 제주특별자치도 제주시. Send together with name."New value: +"Korean issuing region in Korean, e.g. 서울특별시 종로구. Required with name; optional with management_number, where it picks the local government that issued a shared number."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "One permit record, a reason no single record was chosen, COUNTRY_NOT_COVERED, or an error.",
+  "properties": {
+    "check_page": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Check Page"
+    },
+    "country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Country"
+    },
+    "covered_countries": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Covered Countries"
+    },
+    "detail": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Detail"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Error"
+    },
+    "found": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Found"
+    },
+    "matched_on": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Matched On"
+    },
+    "next_step": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Next Step"
+    },
+    "record": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Status, category, permit date, record page link and citation.",
+      "title": "Record"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Status"
+    }
+  },
+  "title": "PermitLookupResult",
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-open-world behavior. The description contributes real extra context: coverage limits (KR only, 'not covered yet' elsewhere), the single-record return shape, and the failure mode ('says why no single record could be chosen').

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 with the core action and identifiers, with exclusions and coverage caveats following. It is dense but every sentence adds a constraint; the 'more countries are coming' remark is the only slightly promotional snippet.

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 an output schema present, return-value explanation is a bonus rather than a requirement. The description still covers identifier rules, geographic coverage, and the no-match outcome, so an agent has everything needed to call it correctly.

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%, so the baseline is 3, but the description adds cross-parameter logic beyond the schema: name must accompany region, and region is optional with management_number where it disambiguates shared numbers. That combinatorial guidance is genuinely useful.

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 ('Fetch one accommodation permit record from official South Korean government data') with the exact identifier forms accepted. It also explicitly bounds scope against browsing ('Never lists or browses records'), which separates it from its sibling verify_listing_registration.

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?

Clear about when this applies: it accepts one of the identifier combinations and explicitly excludes pasted listing text. It does not, however, name verify_listing_registration as the alternative for listing-text scenarios, leaving that routing to inference.

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

All SelectBNBs Verify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?