Skip to main content
Glama

대전한콕 Daejeon Hankok

places_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>",
      "category": "<category>"
    },
    "name": "places_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmNo
latYes
lngYes
limitNo
categoryYeshair(헤어) nail(네일) food(맛집) cafe(카페)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavior beyond that — results ordered by proximity and a hard 10km ceiling — but says nothing about pagination (limit default 20, max 50) or what a result record contains.

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 compact sentences with the ordering/radius constraint and the use trigger front-loaded. No filler or restatement of the title.

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?

For a 5-parameter geo-search tool with 20% schema coverage and no output schema, the description leaves too much unspecified: the units and role of lat/lng, the default 1km radius, the limit cap, and how results differ from the many sibling search tools are all unaddressed.

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 only 20%: category is documented in the schema, while lat, lng, km, and limit are bare. The description only loosely implies lat/lng (좌표) and restates the 10km ceiling already encoded as km's maximum; it never clarifies units, the km default of 1, or the limit parameter.

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 operation and resource: find stores around a coordinate, returned nearest-first within a 10km cap. An agent can grasp the core behavior immediately, though it never names or distinguishes itself from siblings like search_places or list_places.

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?

"사용자의 현재 위치나 역·건물 좌표로 찾을 때" gives a clear positive trigger — use it when you have a user's current location or a station/building coordinate. It offers no when-not guidance and does not route the agent to or away from the near-duplicate siblings (search_places, list_places, stylists_near).

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