Skip to main content
Glama
deenesjakoruzh
overstarry

qweather-mcp

by overstarry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

qweather-mcp

대장간 배지

영어 |简体中文

QWeather API를 위한 MCP 서버로, Model Context Protocol(MCP)을 통해 포괄적인 날씨 정보 쿼리 기능을 제공합니다.

✨ 특징

  • 🌤️ 실시간 날씨 쿼리

  • 📅 며칠 날씨 예보 (3/7/10/15/30일)

  • 🔑 간단한 API 키 구성

  • 🔌 사용자 정의 API 기반 URL 지원

  • 🛠️ 완벽한 도구 통합

Related MCP server: OpenWeatherMap MCP Server

📦 설치

스미서리를 통해

권장 사항: Smithery를 사용하여 Claude Desktop에 자동으로 설치:

지엑스피1

수동 구성

  1. 먼저 QWeather 콘솔 에서 API 키를 받으세요.

  2. 서버를 시작합니다:

# stdio server
npx -y qweather-mcp

  1. 환경 변수 구성:

QWEATHER_API_BASE=https://api.qweather.com
QWEATHER_API_KEY=<your-api-key>

JSON 구성

구성 파일에 다음을 추가합니다.

{
  "mcpServers": {
    "qweather": {
      "command": "npx",
      "args": ["-y", "qweather-mcp"],
      "env": {
        "QWEATHER_API_BASE": "<your-api-url>",
        "QWEATHER_API_KEY": "<your-api-key>"
      }
    }
  }
}

🛠️ 사용 가능한 도구

지금 날씨를 알아보세요

지정된 위치의 현재 날씨 정보를 가져옵니다.

날씨 예보 받기

사용자 정의 가능한 예보 일자를 통해 지정된 위치에 대한 날씨 예보 정보를 받으세요.

  • 3일 예보

  • 7일 예보

  • 10일 예보

  • 15일 예보

  • 30일 예보

예측 데이터에는 다음이 포함됩니다.

  • 온도 범위(최소/최대)

  • 낮/밤 날씨 조건

  • 일출/일몰 시간

  • 강수량

  • 습기

  • 바람 상태

  • 자외선 지수

1분마다 강수량 측정

다음 2시간 동안의 분 단위 강수량 예보를 제공합니다. 여기에는 다음이 포함됩니다.

  • 강수 유형(비/눈)

  • 분당 강수량

  • 정확한 시간 예측

  • 실시간 예보 설명

시간당 예보 가져오기

다음을 포함하여 24, 72 또는 168시간 동안의 시간별 날씨 예보를 제공합니다.

  • 온도 변화

  • 날씨 상황

  • 바람의 방향과 세기

  • 상대 습도

  • 기압

  • 강수 확률

  • 구름 범위

날씨 경고 받기

다음을 포함한 실시간 날씨 경고 정보를 제공합니다.

  • 경고 발행 기관

  • 경고 수준 및 유형

  • 자세한 경고 내용

  • 경고 유효 기간

  • 관련 추천

날씨 지수 얻기

다양한 지수 유형을 지원하여 날씨 생활 지수 정보를 제공합니다.

  • 스포츠 지수

  • 세차 지수

  • 드레싱 인덱스

  • 낚시 지수

  • 자외선 지수

  • 관광 지수

  • 알레르기 지수 및 기타 16개 생활지수

공기질 얻기

다음을 포함한 실시간 대기 질 데이터를 제공합니다.

  • AQI 지수

  • 대기질 수준

  • 1차 오염 물질

  • 건강 조언

  • 오염 물질 농도

시간당 공기질 얻기

다음 24시간 동안의 시간별 대기 질 예보를 제공합니다.

  • 시간당 AQI 예측

  • 오염물질 농도 변화

  • 건강영향평가

  • 보호 권장 사항

매일 공기질 측정

향후 3일간의 대기 질 예보를 제공합니다.

  • 일일 AQI 예측

  • 1차 오염 물질 예측

  • 대기 질 수준 변화

  • 건강 보호 조언

🤝 기여하기

문제점과 개선 사항을 환영합니다! 기여 가이드라인을 확인해 주세요.

📄 라이센스

MIT

🔗 관련 링크

Available Tools

2 tools
get-weather-nowC

Get current weather for a location using QWeather API

ParametersJSON Schema
NameRequiredDescriptionDefault
locationYesLocation ID for the city

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided. The description implies a read operation but lacks details about API key requirements, error handling, or response format. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise single sentence. Could be improved by adding a hint about the sibling tool or output format without being verbose.

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 low complexity, the description is incomplete. It does not explain how to obtain the location ID or what the output contains, missing essential context for the agent.

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?

Schema coverage is 100%, with the parameter described as 'Location ID for the city'. The description adds no extra parameter info, so baseline 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 'Get current weather for a location' with a specific API mention. However, it does not differentiate from sibling 'lookup-city', which likely provides city IDs.

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?

No guidance on when to use this tool versus alternatives. The description does not mention that the location parameter might come from the sibling tool 'lookup-city'.

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

lookup-cityC

Look up city information by name

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNameYesName of the city to look up

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the basic action, with no mention of side effects, authentication needs, rate limits, or error handling (e.g., if city not found). This is insufficient for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the action. It could be more structured (e.g., listing what information is returned), but it is not verbose.

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?

For a simple lookup tool with one parameter and no output schema, the description does not specify what fields of city information are returned, nor any behavioral context. This leaves the agent uncertain about the response format.

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?

Schema description coverage is 100% (single parameter well-described in schema). The description adds no extra meaning beyond 'by name', but the schema already provides a clear description. Baseline 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 action 'look up city information by name', specifying verb and resource. However, it does not differentiate from the sibling tool 'get-weather-now', which may also involve city queries. The description lacks detail on what information is returned.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or cases to avoid. The sibling tool exists but is not differentiated.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedget-weather-now
    • First observedlookup-city
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

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one retrieves current weather data, and the other looks up city information. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern using snake_case: get-weather-now and lookup-city. The naming is predictable and clear.

Tool Count3/5

With only 2 tools, the set is on the lower end of reasonable. While it covers the basics, it feels minimal for a weather API, which typically includes more operations like forecasts or alerts.

Completeness2/5

The tool set lacks essential weather features such as forecasts, historical data, or severe weather alerts. For a weather-focused server, the absence of these common operations is a notable gap.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches