Skip to main content
Glama

대전한콕 Daejeon Hankok

search_places

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoryNohair(헤어) nail(네일) food(맛집) cafe(카페)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so safety is covered and the description is not required to restate it. The description does add real behavior the annotations cannot: a two-stage retrieval strategy where Daejeon results are attempted first and only then widened to nationwide stores matched by name or neighborhood. It stops short of describing result ordering within a stage or how limit interacts with the fallback.

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?

Two sentences plus a compact example list, with the core capability front-loaded and the fallback scope immediately after. The examples directly serve query construction rather than padding, so every element earns its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description bears responsibility for explaining what comes back, and it only obliquely implies results are place records. Combined with the unexplained `limit` and the ambiguous query/category interaction, a caller still has gaps for a tool that is otherwise simple and well annotated.

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 coverage is only 33% – query and limit carry no schema descriptions – so the description must compensate, and it does partially by spelling out the five things `query` accepts and giving four concrete query examples. The `category` enum is already self-documenting in the schema, but `limit` receives no explanation at all, and it is unstated whether category and query are combined or category overrides the text search.

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 concrete verb-and-resource pair ('가게 이름·메뉴·시술·세부 업종·주소로 찾는다' – find places by name/menu/service/sub-category/address), which is far more specific than 'search'. It also states the geographic scope (Daejeon first, then nationwide), which implicitly separates it from proximity-based siblings like places_near, but it never names an alternative explicitly.

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 through the enumerated search keys and the sample queries ('마라탕', '둔산동 미용실'), so an agent can infer this is the free-text lookup tool. However, there is no explicit when-not-to-use guidance and no named alternative (e.g. list_places, places_near, get_place) for structured or proximity-based lookups, leaving routing to inference.

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