Skip to main content
Glama
kimbongjune

tour-crowding-mcp

by kimbongjune
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tour-crowding-mcp

No user-submitted related servers found.

    Related Servers

    • weather-forecast-mcp

      hlucent
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying South Korean meteorological observation data and short-term forecasts by region name or grid coordinates via the MCP protocol.
      MIT

    • mcp-tour

      tjwodud04
      F
      license
      Not graded
      quality
      C
      maintenance
      Integrates the Korea Tourism Organization's API to provide tourist spot recommendations and detailed information, including attractions, food, and accommodation.
      1
      -

    • MCPortal

      yonghwan1106
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridges Korean public data APIs (data.go.kr) into MCP with automatic OpenAPI normalization, quota management, caching, and backoff. Enables natural language interaction with Korean government data through MCP.
      Apache 2.0

    • airkorea-forecast-alert-mcp

      hlucent
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Korean air quality forecasts, weekly ultrafine dust forecasts, high-concentration PM2.5 forecasts, particulate matter alarm statuses, ozone advisories, and yellow dust advisories from the AirKorea OpenAPI.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly separate roles—area resolution, attraction lookup, detail, crowding, festivals, and quota usage are easy to tell apart. However, get_crowding and recommend_quiet both deal with crowding-derived information, and find_attraction versus list_places could initially be confused, though the descriptions provide enough guidance.

    Naming Consistency4/5

    The tool names follow a mostly consistent snake_case verb-first pattern such as find_*, get_*, list_*, and resolve_*. Minor deviations include usage, which is a bare noun, and recommend_quiet, which uses an adjective rather than a noun object.

    Tool Count5/5

    Eight tools is well within the ideal range and each tool covers a distinct part of the tourism/crowding workflow: area resolution, attraction search and detail, crowding data, quiet recommendations, category place lists, festivals, and quota checking. Nothing feels redundant or unnecessary.

    Completeness4/5

    The toolset covers the core workflow end-to-end, including resolving areas, finding and inspecting attractions, getting crowding forecasts, listing places and festivals, and monitoring usage. Minor gaps exist—such as no direct combination of category lists with crowding and no explicit date-scoped crowding query—but the descriptions acknowledge these limitations and give agents a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources