Skip to main content
Glama
Sign In
OpenWeatherMap MCP Server

OpenWeatherMap MCP Server

by robertn702
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-daily-forecast

Retrieve daily weather forecasts for up to 8 days using OpenWeatherMap MCP Server. Input location, units (metric, imperial, standard), and forecast days. Includes today's weather option.

Instructions

Get daily weather forecast for up to 8 days

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": {
      "location": "<location>"
    },
    "name": "get-daily-forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to forecast (1-8, default: 8)
include_todayNoInclude today's forecast (default: false)
locationYesCity name (e.g., 'New York') or coordinates (e.g., 'lat,lon')
unitsNoTemperature units: metric (Celsius), imperial (Fahrenheit), or standard (Kelvin)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 the 8-day limit but doesn't cover other critical aspects like rate limits, authentication needs, error handling, or what the output looks like (e.g., format, data fields). For a tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose without unnecessary words. It earns its place by clearly stating the tool's function and key constraint (8-day limit), making it easy to parse.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the forecast includes (e.g., temperature, precipitation), how results are structured, or any behavioral traits like rate limits. For a tool with 4 parameters and rich functionality, this leaves too much undefined 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 description coverage is 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain interactions between parameters like 'days' and 'include_today'). Baseline 3 is appropriate when the schema does the heavy lifting.

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 daily weather forecast') and resource ('weather forecast'), specifying the scope ('for up to 8 days'). It distinguishes from siblings like 'get-current-weather' by focusing on daily forecasts, though it doesn't explicitly differentiate from 'get-weather-forecast' which might be similar.

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-hourly-forecast' or 'get-weather-forecast'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Deploy Server

Other Tools

Related Tools