Skip to main content
Glama
hyen43

Model Context Protocol Server

by hyen43

weather

Get current weather conditions for any city to plan activities or check local forecasts. This tool retrieves temperature, conditions, and other meteorological data.

Instructions

도시의 날씨 정보를 가져오기

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYes도시 이름 (예: 런던)

Implementation Reference

  • The main handler function for the 'weather' tool. It takes a city name and returns mock weather data including temperature, condition, and humidity.
    async execute({ city }) {
        // 실제 API 호출로 대체해야 합니다
        return {
            city,
            temperature: 22,
            condition: "맑음",
            humidity: 45,
        };
    }
  • Input schema using Zod, requiring a 'city' string parameter with description.
    schema = {
        city: {
            type: z.string(),
            description: "도시 이름 (예: 런던)",
        },
    };
  • Tool class definition extending MCPTool and setting the name to 'weather', effectively registering its identity.
    class WeatherTool extends MCPTool {
        name = "weather";
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states what the tool does ('가져오기' - get/fetch), implying a read operation, but doesn't disclose any behavioral traits like rate limits, authentication needs, error conditions, or what format the weather information returns. For a tool with no annotations, this is insufficient.

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 extremely concise with a single sentence that directly states the tool's purpose. It's front-loaded with the core functionality and contains no wasted words or redundant information, making it highly efficient.

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 the tool's complexity (simple single-parameter query) and lack of annotations and output schema, the description is incomplete. It doesn't explain what weather information is returned (e.g., temperature, conditions), potential errors, or usage constraints. For a tool with no structured output or behavioral annotations, more context is needed.

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 schema description coverage is 100%, with the single parameter 'city' fully documented in the schema. The description adds no additional meaning beyond the schema, as it doesn't explain parameter usage, constraints, or examples beyond what's already provided. With high schema coverage, the baseline score of 3 is appropriate.

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: '도시의 날씨 정보를 가져오기' (Get weather information for a city). It specifies the verb ('가져오기' - get/fetch) and resource ('날씨 정보' - weather information) with a target scope ('도시' - city). However, it doesn't differentiate from sibling tools like 'weather_api', so it doesn't reach a perfect score.

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. There are sibling tools like 'weather_api' and 'example_tool', but the description doesn't mention any context, prerequisites, or exclusions for using this specific weather tool over others.

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/hyen43/mcpServer'

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