Skip to main content
Glama

대전한콕 Daejeon Hankok

list_areas

Read-onlyIdempotent

대전한콕이 다루는 대전 동네·업종·상황(태그)과 동네별 가게 수. 다른 도구의 area·category·tag 값을 여기서 고른다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing what the response contains – the covered neighborhoods/categories/tags together with per-neighborhood store counts – which is the main thing an agent needs to know before deciding to call it. It does not describe the response shape or ordering, but that is a minor gap for a zero-parameter reference tool.

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 with no filler: the first describes the payload, the second describes how to use it, in that order. Nothing is redundant or misplaced.

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 zero-parameter, read-only, closed-world lookup with no output schema, the description covers what it returns and how it should be used as a prelude to other calls. Only the exact response format and whether counts are live remain unstated, which is acceptable at this complexity level.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is high. The description still adds semantic value by explaining that the returned values map onto the area, category, and tag parameters of other tools, which frames the output as reusable filter vocabulary.

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 the specific resource this tool enumerates – Daejeon neighborhoods, business categories, and situation tags, plus the store count per neighborhood – so an agent knows it is a reference/enumeration endpoint rather than a search tool. It is phrased as a noun list without an explicit verb, and it does not explicitly contrast itself with siblings like search_places or list_places, but the resource is unmistakable.

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?

The second sentence gives a clear usage rule: pick the area, category, and tag values used by other tools from here. That establishes the intended call order (call this before the filtered sibling tools) without naming specific alternatives or stating exclusions.

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