Skip to main content
Glama
yukit7s

Tokyo WBGT MCP Server

by yukit7s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tokyo WBGT MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-jma

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables you to retrieve JMA weather forecasts, warnings/advisories, and earthquake reports by place name, with no API key required.
      13 npm
      MIT

    • MCP-Weather

      Takatoshi-Miura
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables retrieval of weather information for major cities across Japan using the Japan Meteorological Agency API. Supports weather overviews, precipitation probability, and wind speed data with both local and remote OAuth 2.0 authenticated deployment options.
      3 npm
      MIT

    • japan-climate-stats-mcp

      japan-opendata-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to retrieve and cross-analyze Japanese prefecture- and municipality-level climate and environment statistics—including sunshine, temperature, precipitation, and extreme-heat/frost days—using JIS code normalization, fast local caching, and Parquet export for correlation discovery.
      MIT

    • Japanese Weather MCP

      tsukiyama85
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides weather information for 110 cities across Japan with natural language support for location names in kanji, hiragana, and katakana. Retrieves current weather conditions and forecasts using OpenMeteo API through MCP-compliant tools.
      1
      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 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_all_tokyo_locations retrieves predicted values for all observation points, get_tokyo_realtime_data gets measured values for actual observation points only, and get_tokyo_wbgt_forecast obtains forecast values. There is no overlap or ambiguity between these three functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (all_tokyo_locations, tokyo_realtime_data, tokyo_wbgt_forecast). The naming is perfectly uniform and predictable throughout the set.

    Tool Count5/5

    Three tools is well-scoped for a Tokyo WBGT server focused on location data, real-time measurements, and forecasts. Each tool earns its place without redundancy, and the count is appropriate for the apparent domain scope.

    Completeness4/5

    The tools cover the core WBGT data retrieval needs (locations, real-time, forecasts) for Tokyo, with no obvious dead ends. A minor gap might be historical data or alerts, but agents can work effectively with the provided surface for typical weather/heat index queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources