GridPulse Energy

get_optimal_schedule

Given multiple zones where flexible compute or charging could run, find the best contiguous hour block before a UTC deadline. Returns a ranked list using day-ahead prices per zone and each zone’s current green score. Optimise for lowest price, highest green score, or a balanced blend.

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": {
      "zones": "<zones>",
      "hours": "<hours>",
      "deadline_utc": "<deadline_utc>"
    },
    "name": "get_optimal_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	Yes	Length of the contiguous scheduling window in hours.
`zones`	Yes	Bidding zone codes to compare (e.g. ["DE", "FR", "NO"]).
`deadline_utc`	Yes	ISO 8601 instant — only hours at or before this timestamp are considered (per day-ahead series).
`optimise_for`	No	price = rank by lowest average €/MWh; carbon = rank by green score (higher better); balanced = 50/50 normalized price and green score.	balanced

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 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 provided, the description carries full burden. It discloses the core logic (day-ahead prices, green scores, optimization modes, ranked list) but misses behavioral details like read-only nature, handling of missing data, or exact ranking/tie-break behavior.

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?

Two sentences, front-loaded with purpose, zero fluff. Every clause earns its place while covering the essential inputs, methodology, and output type.

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?

No output schema and no annotations; description says 'ranked list' but doesn't clarify whether the list ranks zones or hour blocks, nor what fields appear in each item. It also doesn't mention behavior when no valid block exists. Missing these details hurts completeness.

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 baseline is 3. The description adds little beyond the schema; 'contiguous' and 'UTC deadline' are already in the schema. It does clarify the optimization intent but not significantly.

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 a specific verb+resource: 'find the best contiguous hour block before a UTC deadline' across multiple zones. It also distinguishes itself from siblings like get_cheapest_window by supporting multiple optimization modes (price, carbon, balanced).

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 a clear use case: 'where flexible compute or charging could run' and 'before a UTC deadline'. It does not explicitly mention alternatives or when not to use, 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?