Skip to main content
Glama

Grid frequency of Continental Europe in Hz (Energy-Charts, Fraunhofer ISE)

get_grid_frequency
Read-only

Free. Measured power grid frequency in Hz (Continental European grid, measured at Freiburg, published by Energy-Charts under CC BY 4.0): the latest reading with its age, the last minute and 15 minutes, today's minimum and maximum with times, the share of today's seconds outside the 50 Hz ±50 mHz standard range, and per-minute means for the last hour. About 2-3 minutes behind real time. Facts only: not a forecast, not a stability score. A small deviation from 50 Hz is normal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_grid_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this as a read-only, open-world operation. The description adds substantive behavioral context beyond those annotations: data source and license, measurement location, publication lag, the exact returned aggregates, and the interpretive caveat that small deviations are normal.

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 definition is front-loaded with the key fact (measured grid frequency in Hz) and then lists the returned readings in a compact, information-dense manner. It is somewhat long as a single sentence plus caveats, but nearly every clause contributes useful scope or interpretation.

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?

There is no output schema and no input schema, so the description must carry the full burden of explaining what comes back. It does so thoroughly, covering freshness, aggregation windows, extrema, out-of-range share, and the meaning of deviations relative to the 50 Hz standard.

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 takes zero parameters, so there are no parameter semantics to explain, and the baseline for a zero-parameter tool is 4. The description correctly avoids inventing parameter behavior and instead focuses on the response content.

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 names a specific resource (measured Continental European power grid frequency in Hz) and enumerates exactly what the tool returns: latest reading with age, last minute and 15 minutes, today's min/max with times, out-of-range share, and per-minute means for the last hour. This is far more specific than a title restatement and lets an agent identify the tool without opening anything else.

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?

It clearly scopes the tool as facts-only and explicitly says it is not a forecast or stability score, which tells the agent when not to use it. It also notes the data is about 2-3 minutes behind real time and that small deviations from 50 Hz are normal, but it does not explicitly point to an alternative tool for forecasting or stability analysis.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.