Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATA_MODENoThe data mode: 'file' (default) or 'api'. Use 'api' to query hospital, bus stop, market, and shop data from the Korean public data API; requires DATA_GO_KR_SERVICE_KEY.file
LOCAL_DATABASE_PATHNoPath to the local SQLite database file used in file mode.data/processed/gyeongbuk.sqlite3
DATA_GO_KR_SERVICE_KEYNoService key for the Korean public data API. Required only when DATA_MODE=api.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_nearby_hospitalsB

Find hospitals within an estimated straight-line walking time.

search_nearby_bus_stopsB

Find nearby stops meeting an estimated daily-service threshold.

search_nearby_marketsA

Find registered traditional markets within an estimated walking time.

recommend_car_free_neighborhoodsC

Rank market-centered areas that pass hospital and bus constraints.

get_age_population_ratioC

Return the resident-population share for an inclusive age range.

get_safety_gradeC

Return an official relative safety grade; lower grades are safer.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinctly different concern: hospital proximity, bus-stop coverage, market-walkability, overall neighborhood recommendation, age ratio, and safety grade. Even the similar 'search_nearby_*' tools are clearly separable by resource type.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: search_nearby_*, recommend_*, and get_*. The naming is predictable and makes the tool surface easy to navigate.

Tool Count5/5

Six tools is a well-scoped size for this domain. Each tool fills a clear role in the workflow of finding and justifying car-free neighborhoods, with no padding or obvious duplication.

Completeness4/5

The set covers the core workflow: find nearby amenities, receive neighborhood recommendations, and retrieve demographic or safety context. It is not a CRUD system, so no create/update/delete is needed, though richer facility details or result filtering could add depth.

Maintenance

ActivityMaintained
ResponsivenessNo issues