Skip to main content
Glama

대전한콕 Daejeon Hankok

디자이너 상세

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

Input Schema

NameRequiredDescriptionDefault
idYes디자이너 id (링크 /d/{id} 의 id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 covered. The description adds the useful behavior that results are scoped to one designer plus their shop and shop-mates, but says nothing about missing-id behavior, auth, or rate limits. Adequate but not rich beyond the annotations.

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 dense sentence that front-loads the resource and then lists returned fields without filler. It reads as a field inventory rather than prose, but nothing is wasted.

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?

No output schema exists, so enumerating the returned fields is exactly the right compensation and it is done thoroughly. The remaining gap is selection guidance relative to the search/lookup siblings, which the description never addresses.

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?

Only one parameter (id) with 100% schema description coverage, including the /d/{id} link hint. The description adds no further meaning about the id format or where to obtain it, so the schema 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?

Names the specific resource ("헤어 디자이너 상세") and enumerates what it exposes: 소속 샵, 주소, 잘하는 시술, 스타일 사진 수, 네이버 예약 주소, 샵 시술 가격, 같은 샵 다른 디자이너. An agent knows exactly what it gets back, but nothing distinguishes it from siblings like search_stylists or stylists_near.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to call this versus search_stylists/stylists_near, and no prerequisites. The only usage signal (needing an id) lives in the schema's id description, not in the tool description itself.

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