Skip to main content
Glama
Weather MCP Server

Weather MCP Server

by vihanrs

Get current weather

get-current-weather
Read-onlyIdempotent

Retrieve current weather conditions for a chosen city, with temperature in Celsius or Fahrenheit, to check present weather.

Instructions

get the current weather of selected city

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get-current-weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesthe name of the city you want to get the weather details
unitNoTemperature unit (default: celsius)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that – no data source, freshness, or error behavior – which is acceptable given the rich annotations but not additive.

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?

A single short sentence with no filler or redundancy, though its lowercase phrasing and lack of front-loaded guidance make it minimally structured rather than polished.

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?

For a simple two-parameter read tool with complete schema coverage and full annotations plus no output schema, the description is just barely sufficient. It omits any note on what 'current' returns or how it differs from forecast siblings, leaving only a minimum viable definition.

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%, so both the required 'city' and the 'unit' enum are fully documented in the schema, including the celsius default. The description adds no extra meaning, which meets the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (current weather of a selected city), so the basic operation is clear. However, it never contrasts itself with the sibling tools get-forecast or compare-weather, so the distinguishing word 'current' is left for the agent to infer.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives; an agent must guess whether to call this or get-forecast. Usage is only implied by the tool name.

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