Skip to main content
Glama

대전한콕 Daejeon Hankok

헤어 디자이너 찾기

search_stylists
Read-onlyIdempotent

대전 헤어 디자이너를 이름·잘하는 시술(예: 히피펌, 탈색, 레이어드컷)·샵 이름·동네로 찾는다. query 없이 area 만 주면 그 동네 디자이너(스타일 사진 많은 순). 줄마다 디자이너 페이지·네이버 예약 주소.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_stylists"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo동네 slug(선택, list_areas 참고)
limitNo
queryNo예: '히피펌', '둔산 탈색', '제이라벨'

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, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavior beyond them: the default ranking when only area is supplied (most style photos first) and the per-row return content (designer page plus Naver booking address link), which is valuable given 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.

Conciseness4/5

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

Three short sentences, front-loaded with purpose, then the area-only rule, then output shape. Almost every clause carries information; only the parenthetical examples could be trimmed.

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 read-only search tool with no output schema, the description covers what is searched, the fallback ranking, and the per-result fields. The remaining gap is `limit`/pagination behavior, which is not mentioned anywhere, but overall it is sufficient to call the tool correctly.

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 67%, and the description meaningfully expands `query` by naming what it searches across (name, specialty, shop, neighborhood) and giving examples. However, `limit` has no description in either schema or prose (only default 20 / max 50), leaving one parameter's semantics unstated.

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 states a concrete verb and resource ('대전 헤어 디자이너를 ... 찾는다') and enumerates the searchable facets (name, specialty procedure, shop name, neighborhood). It is clear on its own, but it never distinguishes itself from close siblings such as stylists_near or get_stylist, so an agent cannot route between them from this text 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?

It gives one genuinely useful usage rule: passing area without query yields that neighborhood's designers sorted by style-photo count. That is implied guidance for the area-only case, but there is no explicit statement of when to prefer this over stylists_near or the generic search tools, and no stated prerequisites.

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