Skip to main content
Glama
MinhHieu-Nguyen-dn

Weather MCP Server

server_info

Check the current configuration of the Weather MCP Server to understand its operational settings and capabilities for weather data retrieval.

Instructions

Get information about the current Weather MCP server configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The server_info tool handler function, registered via @mcp.tool() decorator. It provides server configuration details including name, logging setup, API endpoints, available tools list, and logging capabilities.
    @mcp.tool()
    async def server_info(ctx: Context[ServerSession, None]) -> dict:
        """Get information about the current Weather MCP server configuration."""
        await ctx.info("Retrieving server information")
        logger.info("Server info requested")
        
        return {
            "server_name": ctx.fastmcp.name,
            "python_log_level": logging.getLevelName(logger.level),
            "log_file": "weather_mcp.log",
            "nws_api_base": NWS_API_BASE,
            "user_agent": USER_AGENT,
            "available_tools": ["get_alerts", "get_forecast", "server_info"],
            "logging_features": [
                "Standard Python logging to file and console",
                "MCP Context logging (debug, info, warning, error)",
                "Progress reporting for long operations",
                "Structured exception handling"
            ]
        }
Behavior3/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 indicates a read operation ('Get information'), which suggests non-destructive behavior, but doesn't specify details like authentication needs, rate limits, or what specific server info is returned. This is a minimal but adequate disclosure for a simple tool.

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, clear sentence that directly states the tool's purpose without any wasted words. It is front-loaded and efficiently communicates the essential information, making it highly concise and well-structured.

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 simplicity (0 parameters, no output schema, no annotations), the description is complete enough for basic understanding. However, it lacks details on the return format or specific server configuration aspects, which could be helpful for an agent, keeping it at a minimum viable level.

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 tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, earning a high baseline score as it avoids redundancy and is complete in this regard.

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 ('Get information') and target ('current Weather MCP server configuration'), making the purpose unambiguous. It doesn't distinguish from sibling tools like 'get_alerts' or 'get_forecast', which would require explicit comparison, so it falls short of 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 like 'get_alerts' or 'get_forecast'. It implies usage for server configuration info but lacks explicit when/when-not instructions or prerequisites, leaving the agent to infer context.

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/MinhHieu-Nguyen-dn/weather-mcp-server'

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