Skip to main content
Glama

대전한콕 Daejeon Hankok

get_place

Read-onlyIdempotent

가게 상세 — 주소·좌표·영업시간·전화·주차·네이버 예약 주소·메뉴/시술과 가격·(헤어) 소속 디자이너.

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": {
      "category": "<category>",
      "id": "<id>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes가게 id (목록 링크 /p/{category}/{id} 의 id)
categoryYeshair(헤어) nail(네일) food(맛집) cafe(카페)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without prose. The description adds value by inventorying the returned payload (hours, parking, reservation URL, prices), but since there is no output schema, it does not say how those fields are shaped or what happens for missing data (e.g., a place with no Naver reservation).

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?

A single front-loaded sentence fragment: resource label first, then a compact enumeration of returned fields. No filler, no restatement of the tool name as a sentence. The middle-dot list is dense but scannable; it stops just short of being cryptic.

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 telling the agent what the response holds, and it does so thoroughly for a detail endpoint. What is missing is secondary: response field structure, behavior on unknown id, and differentiation from the other retrieval tools in the family.

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%: both parameters are documented in the schema, including an enum for category and a hint that id comes from the /p/{category}/{id} link. The description adds no further parameter meaning, so the baseline of 3 applies.

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 names a specific verb and resource ("가게 상세" = place detail) and then enumerates exactly what that detail contains: address, coordinates, hours, phone, parking, Naver reservation link, menu/treatments with prices, and affiliated designers for hair. This lets an agent know precisely what it gets back. It does not, however, contrast itself against siblings such as list_places or search_places, so the agent must infer that this is the per-id detail fetch.

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 enumerated detail fields plus the required id/category pair suggest this is the follow-up call after a list/search returns a place id. There is no explicit statement of when to prefer this over places_near, search_places, or get_stylist, and no prerequisites or failure conditions are described.

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