Energy Grid MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation4/5
Most tools have distinct purposes (UK carbon, global carbon, prices, power mix), but there is some overlap between get_renewable_percentage_uk and get_uk_power_mix, and between get_uk_carbon_intensity and get_carbon_intensity_forecast. Descriptions help differentiate, but ambiguity is possible.
Naming Consistency3/5
Names are inconsistent: most start with 'get_', but one starts with 'find_'. Some include country prefix ('uk', 'germany', 'eu') while others use 'global'. This mix of conventions reduces predictability.
Tool Count4/5
With 9 tools, the server covers a reasonable scope for energy grid data, including UK and global carbon intensity, power mix, and prices. The count feels appropriate—not too sparse or bloated.
Completeness3/5
The server covers current and forecasted carbon intensity, power mix, and prices, but lacks historical data and more granular queries (e.g., specific generation types). The 'find_greenest_time_window' tool is a nice addition, but there are noticeable gaps.
Average 4.1/5 across 9 of 9 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist. The description provides minimal behavior: returns current share and trend assessment. No info on data source, update frequency, or whether it's destructive.
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?
The description is concise with two sentences and a structured Args/Returns section. However, it is in German while the tool name and parameter are English, causing inconsistency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists. The description does not specify the return format (e.g., percentage number, string). For a simple tool, it lacks detail on what exactly is returned.
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?
The description adds meaning to the region parameter as 'for regional comparison,' but it is brief. Schema coverage is 0%, so the description partially compensates.
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?
The description states the tool gets the renewable percentage in the UK grid, which is clear. However, it does not distinguish it from sibling tools like get_uk_power_mix that may also include renewable data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. The only usage hint is that the region parameter is optional for regional comparison.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the authentication requirement (ELECTRICITY_MAPS_TOKEN) and the return format (breakdown by source in MW). However, it does not mention rate limits, idempotency, or any destructive behavior.
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?
The description is concise with a clear structure: a short sentence followed by Args and Returns sections. No extraneous text. However, it mixes German and English, which could be slightly confusing.
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 the tool has one parameter, no output schema, and no annotations, the description adequately covers the parameter, return value, and authentication. It could be improved by referencing relevant sibling tools for better context, but it is still complete enough for effective use.
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 single parameter 'zone' is described with examples ('DE', 'FR', 'ES', 'US-CAL-CISO') and explained as a zone code. This adds significant meaning beyond the schema's title and type. Schema description coverage is 0%, but the tool description compensates well.
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?
The description clearly states that the tool retrieves the power mix for a global zone, requiring a token. It distinguishes from sibling tools like get_uk_power_mix by specifying 'global zone' and providing examples such as DE, FR, US-CAL-CISO. However, it lacks an explicit verb like 'retrieve' or 'get'.
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?
The description indicates usage by providing zone examples and requiring a token. However, it does not explicitly state when to use this tool over alternatives such as get_global_carbon_intensity or find_greenest_time_window. Usage 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.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It only mentions the time horizon and return format, but lacks details on data freshness, update frequency, API limits, or potential rate limiting. This is a gap for a tool with no annotations.
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 concise and well-structured: a brief one-liner for purpose, followed by parameter details, return format, and a use case. Every sentence provides value without redundancy.
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 the tool has one parameter, no output schema, and multiple siblings, the description covers the main functionality and usage. However, it could be more complete by explicitly distinguishing from get_uk_carbon_intensity and mentioning data source or update frequency.
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 0%, so the description must compensate. It explains hours_ahead with default (24) and max (48), and describes the return value as a list of hourly forecasts. This adds meaning beyond the schema's minimal information.
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 provides a CO2 intensity forecast for the UK power grid up to 48 hours ahead. The verb 'get' and resource 'carbon intensity forecast' are specific, and it distinguishes from siblings like get_uk_carbon_intensity (likely current) and find_greenest_time_window (different purpose).
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 explains the parameter hours_ahead with default and max, and states the return format is a list of hourly forecasts. It gives a use case: planning energy-intensive tasks. However, it does not explicitly compare to sibling tools or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the data source (SMARD/Bundesnetzagentur), states that no registration is needed (indicating open access), and lists the returned fields (price, time period, source). For a simple read-only tool with no parameters, this provides sufficient behavioral transparency beyond the name.
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 extremely concise: three short lines covering output, access, and return fields. Every sentence serves a purpose, and the structure is well-organized with a clear separation of concerns.
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 the tool's simplicity (no parameters, no output schema), the description provides essential information: what is returned, the unit, and the source. It could specify the exact time resolution (e.g., current hour), but it is largely complete for a straightforward data retrieval 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?
The tool has no parameters, and the schema coverage is 100% (trivially). The description adds no parameter-specific information because none exist. The baseline score of 3 is appropriate as the description correctly confirms the tool requires no input.
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 the current wholesale electricity price for Germany in EUR/MWh from SMARD/Bundesnetzagentur. It uses a specific verb ('get'), a specific resource ('wholesale price'), and the domain (Germany) distinguishes it from sibling tools that deal with carbon intensity, power mix, or EU-wide prices.
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 notes that no registration is required, which is a practical usage hint. While it does not explicitly compare with siblings or list exclusions, the tool's specific purpose (German wholesale price) is clearly differentiated from the carbon and power mix tools listed as siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that the tool returns CO2 intensity and power mix, and requires a token. This is sufficient for a read-only tool with no side effects mentioned.
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 concise with two short paragraphs. The first sentence immediately states the purpose, followed by parameter details. No extraneous information.
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?
The description covers the purpose, parameter, and token requirement. However, it does not detail the response structure beyond stating it returns CO2 intensity and power mix. For a simple tool with one parameter, this is mostly adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides only the parameter name 'zone' with no description (0% coverage). The description compensates fully by providing concrete examples and explaining the format, adding significant meaning beyond the schema.
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 gets CO2 intensity for a global zone, specifying the verb and resource. It differentiates from sibling tools by focusing on global zones rather than specific countries like UK or Germany.
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?
The description mentions the required ELECTRICITY_MAPS_TOKEN, which is a necessary condition. However, it does not explicitly state when to use this tool versus alternatives like get_uk_carbon_intensity or get_global_power_mix, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, but description clearly states it returns the best time window with lowest CO2 intensity in next 48 hours plus comparison to current value. Does not disclose potential accuracy limitations or reliance on forecast data, but provides essential behavioral context.
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?
Concise German description with clear sections: purpose, ideal uses, parameters, returns. No fluff, every sentence adds value. Front-loaded with action and resource.
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?
No output schema, but description covers return value (time window with CO2 comparison). Could specify output format (e.g., timestamp range), but sufficient for effective tool use. Sibling tools contextually differentiate this as a scheduling optimizer.
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 has 0% description coverage, but description explains the sole parameter 'duration_hours' as task duration in hours with default of 2. Adds meaningful context beyond schema type and default value.
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?
Clear verb 'findet' (finds) and resource 'grünste Zeitfenster' (greenest time window) with specific use case for AI tasks in UK. Differentiates from sibling tools that provide current or forecast carbon intensity values rather than optimal scheduling windows.
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?
States ideal use cases: GPU training, batch processing, large inference jobs. However, does not explicitly mention when not to use or contrast with alternatives like get_uk_carbon_intensity (which gives current values) or get_carbon_intensity_forecast (which gives forecast series).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It clearly states the output (percentage shares of sources) and implied read-only nature. For a simple, no-parameter tool, this is sufficient transparency, though it lacks mention of potential latency or caching.
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 extremely concise: two short sentences that front-load the main purpose and then detail the return value and a usage note. No superfluous information.
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?
Given the tool has no parameters and no output schema, the description fully explains what the tool returns (energy source percentages) and provides a helpful note about no registration. It is complete for its complexity.
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 input schema has no parameters (0 params), so baseline score is 4. The description correctly focuses on the output and does not need to elaborate on parameters.
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 the current UK power mix with percentage shares for each energy source (Wind, Solar, Nuclear, Gas, Coal). The verb 'get' and resource 'uk power mix' are specific, and the tool is distinct from siblings like 'get_uk_carbon_intensity' and 'get_renewable_percentage_uk' which focus on narrower metrics.
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 indicates it provides the current mix and notes no API registration is needed, which guides usage. However, it does not explicitly mention when not to use this tool versus alternatives, though the simplicity of the tool (no parameters) reduces ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description covers authentication token, return unit (EUR/MWh), and time horizon (next day). It adequately describes behavior for a simple data retrieval tool.
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 concise with three short sections: purpose, args, returns. No wasted words, and critical info (token requirement) is front-loaded.
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?
Given a single parameter, no output schema, and simple behavior, the description provides sufficient context: what it does, what param means, what it returns, and prerequisite (token).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter country_code is explained as EIC code with examples (DE, FR, etc.), adding meaning beyond the schema which only has type and default. Schema coverage is 0%, and the description fully compensates.
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 retrieves day-ahead electricity prices for EU countries, specifying the token requirement. It distinguishes from siblings like get_germany_wholesale_price and carbon intensity tools.
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 explains the token requirement and provides example country codes. It implies usage for EU day-ahead prices vs alternatives, but lacks explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavior. It explains the return values (intensity, index, mix breakdown) and implies a read-only operation. It lacks details on data freshness or update frequency but is adequate for a data retrieval tool.
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 concise with clear Args and Returns sections. Every sentence provides valuable information without unnecessary verbosity.
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?
Given the tool's simplicity and lack of output schema, the description adequately explains return values. It is complete for an AI agent to understand input, output, and side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter (region) with 0% description coverage. The description explains the parameter's purpose, optionality, and provides example values, adding significant meaning beyond the schema.
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 provides current CO2 intensity of the UK power grid with units (gCO2/kWh). It distinguishes from siblings by specifying UK focus and optional regional filtering, making it unambiguous.
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 indicates that leaving the region field empty gives national overview, guiding usage. However, it does not explicitly state when to use this tool versus alternatives like get_uk_power_mix or get_global_carbon_intensity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![energy-grid-mcp-server MCP server](https://glama.ai/mcp/servers/AiAgentKarl/energy-grid-mcp-server/badges/card.svg)](https://glama.ai/mcp/servers/AiAgentKarl/energy-grid-mcp-server)

Score Badge

Copy to your README.md:

[![energy-grid-mcp-server MCP server](https://glama.ai/mcp/servers/AiAgentKarl/energy-grid-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/AiAgentKarl/energy-grid-mcp-server)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AiAgentKarl/energy-grid-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server