Skip to main content
Glama
Sign In

Energy Charts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Public Power

public_power
Read-onlyIdempotent

Electricity generation broken down by production type (solar, wind, nuclear, gas, etc.) for a country over a date range. Returns {unix_seconds, production_types:[{name, data}]}; each series' data array is timestamp-aligned to unix_seconds. Power in MW.

Input Schema

NameRequiredDescriptionDefault
endNoOptional end date, YYYY-MM-DD. Defaults to today.
startNoOptional start date, YYYY-MM-DD. Defaults to 7 days ago.
countryYes2-letter lowercase country code, e.g. "de", "fr", "es", "pl", or "all" for the EU aggregate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "de"
+  },
+  {
+    "country": "all",
+    "end": "2024-01-07",
+    "start": "2024-01-01"
+  }
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / end / description
      Previous value: -"End date, YYYY-MM-DD."New value: +"Optional end date, YYYY-MM-DD. Defaults to today."
    • changedInput schema / properties / start / description
      Previous value: -"Start date, YYYY-MM-DD."New value: +"Optional start date, YYYY-MM-DD. Defaults to 7 days ago."
    • changedInput schema / required
      Previous value: -[
-  "country",
-  "start",
-  "end"
-]New value: +[
+  "country"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint, indicating safety. Description adds details on return structure (unix_seconds, production_types), timestamp alignment, and units (MW), going beyond annotations. No contradiction.

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 plus return format note. Purpose is front-loaded, details are concise, and every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given annotations and no output schema, the description covers input, output structure, and units. Missing error handling or data availability details, but sufficient for a read-only query tool.

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 covers all parameters with descriptions; description adds examples and context (e.g., country codes). However, the description does not significantly enhance understanding beyond what the schema 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?

Description clearly states it returns electricity generation by production type for a country over a date range. It specifies the return format and units, distinguishing it from siblings like total_power, electricity_price, etc.

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?

Describes the tool's functionality and parameters but does not explicitly guide when to use it over siblings (e.g., total_power, generation_mix). The context is implied but not explicit.

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

All Energy Charts toolsInspect
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