Skip to main content
Glama

climatepulse

Assess current weather, forecasts, severe alerts, air quality, wildfire smoke, and agricultural conditions globally to inform planning and safety decisions.

Instructions

ClimatePulse: Global climate and weather intelligence API. Open-Meteo real-time weather + AI synthesis. Severe weather assessment, air quality monitoring, wildfire smoke tracking, agricultural grow-day modeling, cl

Coverage: Global

Endpoints: • now ($0.10): Current conditions • forecast ($0.10): Multi-day forecast • activity ($0.10): Activity weather assessment • severe ($0.10): Severe weather and preparedness • compare ($0.10): Location climate comparison • air ($0.10): Real-time air quality + health risk assessment • smoke ($0.10): Wildfire smoke tracking and respiratory risk assessment • grow ($0.10): Agricultural grow-day modeling and frost date analysis • event ($0.10): Event weather suitability and planning assessment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: now | forecast | activity | severe | compare | air | smoke | grow | event
langNolang
locationNoCity name or location (e.g. Denver, CO)
unitsNoDefaults to imperial (°F, mph, inches)
daysNoNumber of days (1–7, default 7)
activityNoactivity
locationsNoComma-separated list of 2–4 locations (e.g. Miami,Seattle,Denver)
purposeNoComparison purpose (e.g. vacation, relocation, sports)
cropNoTarget crop or plant type
dateNodate
event_typeNoevent_type
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only nature, rate limits, or authentication. It mentions 'global coverage' and pricing but omits explicit statements about idempotency, safety, or side effects. The API appears read-only based on endpoint names, but this is not stated.

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 front-loaded with a clear purpose and includes a structured list of endpoints. However, it includes pricing details that may not be essential for tool selection, slightly reducing conciseness.

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 complexity (11 parameters, multiple endpoints) and no output schema, the description should clarify return formats, parameter dependencies per action, and usage patterns. It lacks these details, making it incomplete for effective use.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's descriptions, which are minimal (e.g., 'activity' described as 'activity'). It does not explain how parameters relate to endpoints or provide examples.

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

Purpose5/5

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

The description clearly states it is a climate and weather intelligence API with specific endpoints for various weather-related queries. It differentiates from sibling tools by its focus on climate/weather, as siblings like 'gridpulse' or 'harvestpulse' suggest different domains.

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 does not provide guidance on when to use this tool versus alternatives. It lists endpoints but lacks context on selection criteria or conditions when other tools might be better suited.

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/GTCC777/pulsenetwork-mcp'

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