Skip to main content
Glama

대전한콕 Daejeon Hankok

대전한콕 검색

search
Read-onlyIdempotent

맛집·카페·헤어·네일 가게(대전은 자세히, 전국은 이름·동네로)와 대전 헤어 디자이너를 검색한다. 결과 id 를 fetch 로 열면 상세(영업시간·가격·예약 주소)가 나온다.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes예: '둔산동 마라탕', '유성 젤네일', '히피펌', '성수동 카페', '해운대 국밥'

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: nationwide queries only match on name/neighborhood while Daejeon gets detailed matching, and the id returned by search is the handle for fetch. It does not mention result limits, pagination, or ranking, which keeps it off a 5.

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, both load-bearing: the first defines coverage scope, the second defines the follow-up action. Scope is front-loaded and there is no filler or repetition of the tool name.

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?

For a single-parameter search tool with full annotation coverage and no output schema, the description covers what is searched, how coverage varies by region, and what the resulting id unlocks via fetch. The remaining gap is result volume and ordering behavior, which an agent would still have to discover empirically.

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?

There is only one parameter and schema description coverage is 100%, with concrete Korean example queries (둔산동 마라탕, 유성 젤네일, 히피펌). The description adds no syntax, format, or matching-mode detail beyond what the schema examples already convey, so the baseline 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 enumerates the resources covered: 맛집·카페·헤어·네일 가게 plus 대전 헤어 디자이너. It also states the coverage split (Daejeon in detail, nationwide by name/neighborhood), which lets an agent predict result quality. It stops short of naming the sibling search_places / search_stylists tools, so differentiation is only partial.

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 rather than stated: the tool is a general entry-point search, and the description tells the agent what to do next (open a result id with fetch). There is no explicit when-to-use / when-not-to-use guidance versus search_places or search_stylists, which cover overlapping ground. The fetch hand-off is the strongest routing signal present.

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