Skip to main content
Glama

대전한콕 Daejeon Hankok

주변 디자이너

stylists_near
Read-onlyIdempotent

좌표 주변 헤어 디자이너(가까운 순, 최대 10km). 사용자 위치·역 근처에서 디자이너를 고를 때.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "stylists_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmNo
latYes
lngYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already certify read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add what they cannot say. It does add two genuinely non-structural traits: results are ordered nearest-first, and the search radius is hard-capped at 10km. It omits any note on what the records contain or how paging/count interacts with the radius.

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 short sentences, scope first (좌표 주변, ordering, radius cap) then usage context — no filler and nothing buried. Every clause earns its place.

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

Completeness2/5

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

With four undocumented parameters and no output schema, the definition should say what a result entry looks like (stylist identity, distance, etc.) and how limit behaves relative to the radius. Missing both leaves an agent able to call the tool but unable to predict its return shape or size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and only partially does so: it clarifies that lat/lng define a coordinate and that km is a distance bounded at 10km. The limit parameter (default 20, max 50) and the km default of 2 are never explained, leaving two of four parameters with no semantic guidance anywhere.

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 a concrete resource (헤어 디자이너) and a concrete spatial scope (좌표 주변, 가까운 순, 최대 10km), which lets an agent distinguish it from a generic keyword search such as search_stylists. It stops short of explicitly contrasting itself with the near-duplicate siblings places_near / search_places, so it is clear but not fully disambiguating.

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

Usage Guidelines4/5

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

'사용자 위치·역 근처에서 디자이너를 고를 때' states the selection context explicitly, so an agent knows this is the geo-proximity path rather than a name/keyword lookup. There are no stated exclusions or named alternatives (e.g., when to prefer search_stylists for a specific designer), which keeps it below a 5.

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