Skip to main content
Glama
yukit7s
by yukit7s

get_tokyo_wbgt_forecast

Retrieve WBGT heat index forecasts for Tokyo locations to assess heat stroke risk and plan outdoor activities safely.

Instructions

東京都のWBGT(暑さ指数)予測値を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNo東京都内の観測地点(tokyo, hachioji, fuchu, nerima, ome, ogochi, edogawa)tokyo

Implementation Reference

  • The handler function that executes the tool logic for get_tokyo_wbgt_forecast. It calls the WBGTService to fetch data and returns it as JSON string in MCP content format.
    private async handleGetTokyoWBGTForecast(location: string): Promise<any> {
      const data = await this.wbgtService.getTokyoWBGTForecast(location as TokyoLocation);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the get_tokyo_wbgt_forecast tool, specifying the location parameter with enum values.
    inputSchema: {
      type: "object",
      properties: {
        location: {
          type: "string",
          description: "東京都内の観測地点(tokyo, hachioji, fuchu, nerima, ome, ogochi, edogawa)",
          enum: ["tokyo", "hachioji", "fuchu", "nerima", "ome", "ogochi", "edogawa"],
          default: "tokyo"
        }
      },
    },
  • src/index.ts:38-52 (registration)
    Registration of the get_tokyo_wbgt_forecast tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_tokyo_wbgt_forecast",
      description: "東京都のWBGT(暑さ指数)予測値を取得します",
      inputSchema: {
        type: "object",
        properties: {
          location: {
            type: "string",
            description: "東京都内の観測地点(tokyo, hachioji, fuchu, nerima, ome, ogochi, edogawa)",
            enum: ["tokyo", "hachioji", "fuchu", "nerima", "ome", "ogochi", "edogawa"],
            default: "tokyo"
          }
        },
      },
    },
  • Supporting service method that implements the core logic: maps location to ID, fetches CSV from API, parses it using utility.
    async getTokyoWBGTForecast(location: TokyoLocation): Promise<WBGTData> {
      const locationId = LOCATION_ID_MAP[location];
      if (!locationId) {
        throw new Error(`Unknown location: ${location}. Available: ${Object.keys(LOCATION_ID_MAP).join(", ")}`);
      }
    
      const url = `${WBGT_API_BASE_URLS.forecast}yohou_${locationId}.csv`;
      
      try {
        const response = await fetch(url);
        if (!response.ok) {
          throw new Error(`HTTP error! status: ${response.status}`);
        }
        
        const csvData = await response.text();
        return parseWBGTForecastCSV(csvData, location);
      } catch (error) {
        throw new Error(`Failed to fetch WBGT data: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does (retrieves forecast data) without mentioning any behavioral traits like rate limits, authentication requirements, data freshness, or response format. For a data retrieval tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence in Japanese that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what format the forecast data returns, what time periods it covers, or any limitations. For a forecast retrieval tool, users need to know what kind of data to expect beyond just 'WBGT forecast values'.

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

Parameters3/5

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

The description adds no parameter information beyond what's already in the schema (which has 100% coverage). The schema fully documents the single 'location' parameter with its enum values and default. The description doesn't provide additional context about parameter usage or meaning, so it meets the baseline for high schema coverage.

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 clearly states the tool's purpose: '東京都のWBGT(暑さ指数)予測値を取得します' (Get WBGT forecast values for Tokyo). It specifies the verb (取得/retrieve) and resource (WBGT forecast for Tokyo), but doesn't distinguish it from sibling tools like 'get_tokyo_realtime_data' which might provide current rather than forecast data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_all_tokyo_locations' or 'get_tokyo_realtime_data', nor does it explain when forecast data is preferable to real-time data or location listings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yukit7s/cc-get-wbgt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server