Skip to main content
Glama

Swiss energy supply indicators (energiedashboard.ch)

get_energy_dashboard
Read-only

Retrieve daily Swiss energy dashboard data—electricity production, consumption, cross-border flows, spot prices, and gas storage—for recent days or date ranges, with optional aggregation and filters.

Instructions

Daily Swiss energy-supply data from the Federal Office of Energy's energy dashboard: 'electricity_production' (Electricity production by energy source (Swissgrid), GWh/day); 'electricity_consumption' (National and final electricity consumption (Swissgrid), GWh/day); 'electricity_consumption_estimate' (Model-based estimate of national electricity consumption (recent days), GWh/day); 'electricity_consumption_forecast' (Electricity final-consumption forecast min/mean/max (SDSC), GWh/day); 'electricity_cross_border' (Cross-border electricity flows per neighbour and net import, GWh/day); 'electricity_spot_price' (Day-ahead spot price Switzerland, baseload, EUR/MWh); 'gas_cross_border' (Cross-border gas flows per neighbour and net import, GWh/day); 'gas_net_imports_monthly' (Monthly gas net imports (VSG), GWh/month); 'gas_storage_eu' (Gas storage levels EU and neighbouring countries, TWh / % of capacity). Returns the last last_days (default 30) or a date range, optionally aggregated by week/month/year (energy summed, prices/levels averaged) and filtered to one category (production: 'Kernkraft', 'Flusskraft', 'Speicherkraft', 'Photovoltaik', 'Wind', 'Thermische'; gas storage: 'EU', 'Germany', 'Italy', …). Example: {series: 'electricity_production', aggregate: 'month', from: '2025-01-01'}.

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": {
      "series": "<series>"
    },
    "name": "get_energy_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (inclusive)
fromNoStart date YYYY-MM-DD (or YYYY-MM for monthly series)
seriesYesWhich indicator
categoryNoOnly this category (energy source or storage region)
aggregateNoAggregate to weeks, months or yearsday
last_daysNoWithout `from`: how many most recent dates to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the load and does add real behavioral detail: aggregation semantics differ by data type (energy summed, prices and levels averaged), the default window is 30 days with a date-range alternative, and each series' unit is given. It stops short of discussing data latency, upstream availability, or the shape of the returned records.

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?

Front-loaded with the source and dataset scope, and every clause — series definitions, units, aggregation rule, example — carries information the agent needs. The series list is a dense semicolon run-on rather than a scannable structure, which costs some readability but no content is wasted.

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?

Inputs are thoroughly covered, but this is a six-parameter, nine-series tool with no output schema, and the description says nothing about the returned record structure, field names, or how heterogeneous series (daily GWh/day, monthly GWh/month, min/mean/max forecasts) are laid out. Enough to select and invoke correctly, but an agent must discover the response shape empirically.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 goes beyond it by supplying the concrete category domain values per series ('Kernkraft', 'Flusskraft', 'Speicherkraft', 'Photovoltaik', 'Wind', 'Thermische' for production; 'EU', 'Germany', 'Italy' for gas storage), which the schema leaves as a generic free string. It also clarifies the payment/aggregation arithmetic applied to each series and gives a canonical invocation example.

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?

Names the concrete resource (daily Swiss energy-supply data from the Federal Office of Energy dashboard) and enumerates all nine series with their measures and units, so the agent knows exactly what data is retrievable. It never names or contrasts a sibling (e.g. get_electricity_tariff or get_current_measurements), so differentiation is left implicit.

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

Usage Guidelines3/5

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

Usage guidance is confined to internal parameter mechanics: the last_days-vs-date-range choice, the aggregation option, and a worked example call. There is no explicit statement of when this tool is the right choice versus a neighboring energy/data tool, nor any stated exclusions.

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