Skip to main content
Glama

대전한콕 Daejeon Hankok

list_places

Read-onlyIdempotent

대전 한 동네의 한 업종 가게 목록(가까운 순, 사진 있는 곳 먼저). 줄마다 주소·예약·영업시간·가격대·주차·쿠폰. tag 를 주면 그 상황(늦게까지·주차·만원 이하 등)만.

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": {
      "area": "<area>",
      "category": "<category>"
    },
    "name": "list_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo상황 거르기(선택). cheap(만원 이하, 맛집) late(밤 10시 넘어서까지, 맛집·카페) parking kids pet localpay booking coupon
areaYes동네 slug (list_areas 참고). 예: dunsan(둔산동), yuseong(유성), eunhaeng(은행동)
limitNo
categoryYeshair(헤어) nail(네일) food(맛집) cafe(카페)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond them: proximity/photo-first sorting and the exact per-row payload (address, booking, hours, price band, parking, coupon), which matters because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments, front-loaded with the core scope, then ordering, then row contents, then the optional tag. Every clause carries information and nothing is padded.

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 usefully enumerates returned fields and describes sort order, which is the main thing an agent could not otherwise know. Remaining gap is the limit/pagination behavior, which is only implied by the schema default of 30 and maximum of 100.

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 75%, close to the threshold where the schema does the heavy lifting, and the enums for tag/area/category are already documented inline with examples. The description restates that tag filters to 'only that situation' but adds nothing about limit or default behavior beyond the schema's own constraints.

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?

States a specific verb and resource — a list of shops in one neighborhood for one category — plus the ordering rule (nearest first, photo-bearing shops first). It does not name or contrast with siblings such as search_places or places_near, so the agent must infer the distinction from the description alone.

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 implied by the required area+category framing and by the note that supplying a tag narrows to that situation, which is effectively a when-to-use hint. There is no explicit statement of when to prefer this over search_places or places_near, and no exclusions.

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