Skip to main content
Glama

fetch_weather

Get current weather conditions for any city to inform planning and decision-making.

Instructions

Fetch current weather for a city

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYes

Implementation Reference

  • The handler function for the 'fetch_weather' tool, decorated with @mcp.tool() for registration. It asynchronously fetches weather data for the given city using httpx to query a weather API endpoint.
    @mcp.tool()
    async def fetch_weather(city: str) -> str:
        """Fetch current weather for a city"""
        async with httpx.AsyncClient() as client:
            response = await client.get(f"https://api.weather.com/{city}")
            return response.text
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 states the tool fetches current weather but doesn't mention any behavioral traits like rate limits, error conditions, authentication needs, data freshness, or what format the weather data returns. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 at just 5 words, front-loading the essential information with zero wasted words. Every word earns its place by contributing to understanding the tool's function. No unnecessary elaboration or repetition is present.

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 has no annotations, no output schema, and 0% schema description coverage, the description is insufficiently complete. It covers the basic purpose but lacks crucial information about behavior, return values, parameter details, and usage context that would be needed for effective tool invocation.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. It mentions 'for a city' which implies the city parameter, but doesn't add any semantic details beyond what's obvious from the parameter name. No information about city format, validation, examples, or constraints is provided, leaving the parameter poorly documented.

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 verb ('fetch') and resource ('current weather for a city'), making the tool's purpose immediately understandable. It doesn't distinguish from siblings, but since there are no sibling weather tools, this is adequate. The description avoids tautology by not just repeating the tool name.

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 constraints. It simply states what the tool does without context about when it's appropriate or inappropriate to invoke it. There are no explicit usage instructions or exclusions mentioned.

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/vs4vijay/espresso-mcp'

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