Skip to main content
Glama

Carbon

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Generation Mix

get_generation_mix
Read-onlyIdempotent

Check current UK electricity grid composition by source percentage (gas, coal, wind, solar, nuclear, hydro, biomass, imports). Use to understand real-time grid energy mix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesEnd time of the generation mix period (ISO 8601)
fromYesStart time of the generation mix period (ISO 8601)
generation_mixYesCurrent electricity generation mix by fuel source and percentage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "from": {
+      "description": "Start time of the generation mix period (ISO 8601)",
+      "type": "string"
+    },
+    "generation_mix": {
+      "description": "Current electricity generation mix by fuel source and percentage",
+      "items": {
+        "properties": {
+          "fuel": {
+            "description": "Fuel type or generation source (e.g., gas, coal, wind, solar, nuclear)",
+            "type": "string"
+          },
+          "percentage": {
+            "description": "Percentage of electricity generated by this fuel type",
+            "type": "number"
+          }
+        },
+        "required": [
+          "fuel",
+          "percentage"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "to": {
+      "description": "End time of the generation mix period (ISO 8601)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "generation_mix"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the tool as read-only and non-destructive. The description adds useful behavioral context by specifying 'current' and 'real-time', indicating the data is a live snapshot rather than historical. It also enumerates the energy sources included (gas, coal, wind, etc.), clarifying the scope of the returned data beyond what annotations provide.

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 short sentences, front-loaded with the action and resource. The first sentence states the core purpose and lists data sources; the second gives a brief use case. No unnecessary words or repetition.

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

Completeness5/5

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

For a simple read-only tool with no parameters and an output schema, the description covers all needed context: what it does (grid mix by source), geographic scope (UK), temporal nature (current/real-time), and a use case. The annotation and output schema fill in safety and return-structure details, so nothing critical is missing.

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?

The tool has zero parameters and the schema is trivially complete. With no parameters to document, the baseline is 4. The description needs no additional parameter information, and it does not attempt to invent any.

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 the tool's function: 'Check current UK electricity grid composition by source percentage.' It specifies the exact resource (UK grid mix) and the data provided (source percentages for gas, coal, wind, etc.). This distinguishes it from related sibling tools like get_intensity, which focus on carbon intensity rather than generation mix.

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 provides clear usage context: 'Use to understand real-time grid energy mix.' It implies this tool is for real-time generation mix queries. However, it does not explicitly mention alternatives or when not to use it, such as for historical data or regional breakdowns, which are covered by sibling tools like get_intensity_by_date or get_regional_intensity.

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

All Carbon 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