GridPulse Energy

get_weather

Get current wind speed (m/s), solar radiation (W/m²), and temperature (°C) for any supported zone. Useful for understanding why electricity prices are high or low (e.g. low wind = less renewable generation = higher prices), or for correlating weather with generation mix.

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": {
      "zone": "<zone>"
    },
    "name": "get_weather"
  }
}

Input Schema

Name	Required	Description	Default
`zone`	Yes	Bidding zone code e.g. DE, GB, NO, CAISO. Use get_supported_zones for full list.
`forecast`	No	If true, returns 48-hour forecast instead of current conditions.

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 18, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden for behavioral disclosure. It provides units and indicates 'current' conditions, but omits the forecast option and any error handling. This is minimal but not misleading.

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 two sentences, front-loaded with the core purpose and units, and includes only relevant use-case details. No unnecessary words.

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?

The description does not mention the forecast parameter, which is a notable omission given it is a primary feature. It also doesn't direct users to get_supported_zones for valid zones, though the schema covers this. Without an output schema, the description should be more comprehensive.

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% for both parameters, so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides.

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 retrieves weather data (wind speed, solar radiation, temperature) for a zone, using a specific verb and resource. It distinguishes itself from sibling tools focused on prices, carbon, and schedules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit use cases: understanding electricity price fluctuations and correlating weather with generation mix. It does not mention alternative tools or when not to use it, but the context is clear enough.

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

All GridPulse Energy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?