Skip to main content
Glama
enesjakozh
acxelerator

mcp-tenki

by acxelerator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

mcp-tenki

A MCP server with weather of Japan

Setup

$ uv sync

Running Server

Run without clone

{
    "mcpServers": {
        "tenki": {
            "command": "uvx",
            "args": ["--from", "git+https://github.com/acxelerator/mcp-tenki.git", "mcp-tenki"]
        }
    }
}

Run with clone

{
    "mcpServers": {
        "tenki": {
            "command": "uv",
            "args": ["--directory", "/PATH/TO/REPOSITORY/mcp-tenki/mcp_tenki", "run", "main.py"]
        }
    }
}

Available Tools

1 tool
get_forecastB
Get forecast for a location in Japan

Args:
    prefecture: Name of the prefecture of Japan (in English alphabets, e.g.) "Hokkaido", "Tokyo", "Osaka", etc.)
ParametersJSON Schema
NameRequiredDescriptionDefault
prefectureYes

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions what the tool does but doesn't describe how it behaves—no information about rate limits, authentication needs, error handling, or what the forecast output contains. This leaves significant gaps for an agent to understand the tool's operation.

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 appropriately sized and front-loaded, with the main purpose stated first followed by parameter details. It avoids unnecessary fluff, though the structure could be slightly improved by separating the purpose and parameter sections more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter semantics but lacks behavioral details and output information, leaving some gaps for complete understanding.

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

Parameters4/5

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

The description adds meaningful context for the single parameter 'prefecture' by specifying it must be a name in English alphabets and providing examples like 'Hokkaido', 'Tokyo', 'Osaka'. This compensates well for the 0% schema description coverage, giving the agent practical guidance on valid input values.

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 with a specific verb ('Get') and resource ('forecast for a location in Japan'), making it immediately understandable. However, it doesn't distinguish from siblings since none exist, so it can't achieve the highest score for sibling differentiation.

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, prerequisites, or context. It simply states what the tool does without any usage instructions or exclusions.

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. 1 tool updatev0.1.0
    • First observedget_forecast
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as getting forecasts for Japanese locations, making it distinct by default.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (get_forecast), which is consistent and predictable. Since there are no other tools, there is no inconsistency to evaluate.

Tool Count2/5

One tool is too few for a weather forecasting server, as it lacks essential operations like searching locations, getting current conditions, or handling multiple forecast types. This minimal scope will likely cause agent failures due to incomplete functionality.

Completeness2/5

The server is severely incomplete for weather forecasting; it only provides forecasts without supporting related operations like current weather, alerts, or location validation. This creates significant gaps that will hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-weather

    ZiQiangWang
    -
    license
    Not graded
    quality
    D
    maintenance
    get weather
    -

  • 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

  • MCP-Weather

    Takatoshi-Miura
    F
    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.
    7
    -

Appeared in Searches