Skip to main content
Glama

숙소 상세

stay_detail
Read-onlyIdempotent

숙소 하나의 상세 정보(이름·주소·좌표·종류·원장 출처)를 조회한다. 재고는 조회하지 못한다 — 이 서버에 붙은 재고 채널이 0개라 날짜·인원을 줘도 availability는 항상 unknown이다(사유는 unavailable_reason에 실린다). 만실도 빈방 있음도 아니다. 빈방·요금은 stay_booking_link로 원본 검색 링크를 받아 직접 확인하라.

관광공사(tourapi) 행에는 인허가 원장의 폐업 등록과 이름·주소 정확 일치로 대조한 결과가 ledger_closure로 온다 — closed_in_ledger면 원장 기준 폐업이고, 같은 주소의 영업 중 원장 등록도 찾지 못했다(대조한 주소 범위는 note에 있다). closed_in_ledger_address_active면 폐업 등록과 함께 같은 주소에 다른 상호로 영업 중인 원장 등록이 있다(same_address_active) — 같은 업소인지 판정하지 못하니 둘 다 전하라. closed_in_ledger_address_unchecked면 폐업 등록은 있지만 같은 주소의 영업 등록 대조를 이번에 못 했다(확인 안 됨). 폐업 등록을 못 찾은 것은 영업 중의 확증이 아니다.

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": {
      "stay_id": "<stay_id>"
    },
    "name": "stay_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsNo인원(1~30)
checkinNo체크인 YYYY-MM-DD
stay_idYesstay_search가 준 stay_id (예: tourapi:2671267)
checkoutNo체크아웃 YYYY-MM-DD
include_footnotesNotrue면 계산값(건수·요금)의 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다(기본은 행마다 한 줄 요지)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_footnotes
      Added value: +{
      +  "default": false,
      +  "description": "true면 계산값(건수·요금)의 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다(기본은 행마다 한 줄 요지)",
      +  "title": "Include Footnotes",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / stay_id / maxLength
      Added value: +200
  3. Changed2 schema fields changed
    • addedInput schema / properties / guests / maximum
      Added value: +30
    • addedInput schema / properties / guests / minimum
      Added value: +1
  4. Changed3 schema fields changed
    • addedInput schema / properties / guests / description
      Added value: +"인원(1~30)"
    • removedInput schema / properties / guests / maximum
      Removed value: -30
    • removedInput schema / properties / guests / minimum
      Removed value: -1
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that availability is always unknown because zero inventory channels are attached, that the reason surfaces in unavailable_reason, and gives a careful reading guide for ledger_closure states with an explicit caveat that absence of a closure record is not proof of operation. This is exactly the kind of domain caveat annotations cannot carry. It does not, however, mention pagination, latency, authentication, or any rate/size limits.

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 purpose and the decisive 'no inventory' caveat, and every sentence carries information with no filler. It is nonetheless dense and roughly half the text interprets output field values (ledger_closure states, unavailable_reason), which is close to duplicating an output schema's job rather than describing the invocation.

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?

Given a read-only, five-parameter tool with an output schema, the description covers everything an agent needs to call it correctly and interpret the result: scope, the stay_id provenance, the always-unknown availability trap, and the ledger closure interpretation rules. Nothing material is missing.

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 a genuinely useful semantic that the schema cannot express: supplying checkin/checkout/guests does not produce real availability, so those parameters are effectively inert for the question most users would bring. It does not clarify date format or guest-range behavior beyond the schema, hence not a 5.

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?

Opens with a specific verb + resource + enumerated fields (이름·주소·좌표·종류·원장 출처), then explicitly carves out what it does NOT return (재고/availability). It distinguishes itself from siblings by name, so an agent can separate it from stay_search and stay_booking_link without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States both when to use it (fetch detail for a stay_id obtained from stay_search) and when not to (any vacancy/rate question), and routes the agent to a named alternative, stay_booking_link, for that case. The 'not full, not vacant' clarification prevents a very plausible misuse of an unknown availability value.

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