Skip to main content
Glama

Gse Frequency

gse_frequency
Read-onlyIdempotent

The Georgian power system's electrical frequency in hertz, from the JSC Georgian State Electrosystem 1-minute real-time export, nominal 50 Hz, and how far it sits from nominal is a direct read on the balance between generation and demand. Carries the same ACT/SUB/NRE quality flag as the grid export.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
max_lookback_slotsNoHow many 1-minute slots to walk back looking for the most recent published reading. Default 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value: the upstream data source, the 1-minute cadence, the nominal 50 Hz reference, the interpretation of deviation as generation/demand imbalance, and the presence of an ACT/SUB/NRE quality flag on the returned reading. What it does not disclose is what happens when no reading is found within the lookback window.

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: the first front-loads what the value is, where it comes from, and why it matters; the second covers the quality flag. There is no filler and no restatement of the tool name.

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?

For a simple single-value read tool with full annotation coverage and a fully described schema, this is close to complete, and the mention of the quality flag offsets the missing output schema. The remaining gap is what the tool returns or errors with when the lookback window yields nothing.

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?

There is a single optional parameter (max_lookback_slots) with 100% schema description coverage, which already explains the walk-back-to-most-recent-published-reading semantics and the default of 15. The description adds no further meaning about this parameter, so the baseline of 3 applies.

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 names a specific resource (the Georgian power system's electrical frequency in hertz), its source (JSC Georgian State Electrosystem 1-minute real-time export), and its nominal value (50 Hz). The verb is only implicit ('is'), and no sibling tool such as gse_grid_now or gse_grid_at is named for contrast, so it falls short of full differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of an alternative tool. The agent must infer that this is for grid-balance monitoring rather than, say, station-level generation, which is covered by other gse_* siblings.

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.