Skip to main content
Glama

Gse Grid Now

gse_grid_now
Read-onlyIdempotent

Georgia's national electricity grid right now: hydro, thermal, wind and solar generation, total generation, cross-border flow on the Azerbaijan, Armenia, Russia (Salkhino/Java/Nakaduli lines) and Turkey tie lines, and total consumption, in MW as a 3-minute moving average. Sourced from the JSC Georgian State Electrosystem real-time system export, published every 3 minutes. Every value carries its QUALITY flag: ACT means actual telemetry, SUB means the operator substituted a figure and NRE means telemetry was not received, so SUB and NRE values are NOT measurements and must not be reported as such.

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_grid_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_lookback_slotsNoHow many 3-minute slots to walk back looking for the most recent published export. Publication lags a few minutes, so the current minute usually does not exist yet. Default 10 (30 minutes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, and the description adds substantial context beyond them: a 3-minute moving average, a 3-minute publication cycle from the JSC Georgian State Electrosystem export, and the ACT/SUB/NRE quality-flag semantics with an explicit warning that SUB and NRE are not measurements. That quality-flag warning is exactly the kind of behavioral detail annotations cannot express. It stops short of describing the response structure or field naming, which keeps it off a 5.

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 data inventory is front-loaded and dense with specifics rather than filler, and the quality-flag caveat at the end earns its place because it changes how results must be reported. There is some repetition around the 3-minute cadence and a long comma-chained sentence that could be split for scanability, but no sentence is purely redundant.

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?

With no output schema, the description carries the burden of explaining return content, and it does so thoroughly: units (MW), smoothing (3-minute moving average), source system, refresh cadence, and per-value quality flags. What is missing is the concrete response shape (field names or how tie lines and totals are keyed), which would help an agent parse results, but the substantive semantics are covered.

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 description coverage is 100% and the single parameter (max_lookback_slots) is fully documented in the schema, including the default, bounds, and the reason for the lookback (publication lag). The description reinforces the 3-minute slot cadence and lag, which is consistent with the parameter, but never mentions the parameter itself or how to tune it, so it adds only marginal meaning beyond the schema. Baseline 3 applies.

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 concrete resource (Georgia's national electricity grid) with an explicit temporal scope ('right now') and enumerates the exact data domains returned: hydro, thermal, wind, solar, total generation, cross-border flows on named tie lines, and total consumption. The 'right now' framing plus the real-time export source clearly separates it from the historical sibling gse_grid_at without needing to name it.

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?

Usage is implied rather than stated: an agent can infer this is the tool for current grid state because of 'right now' and the publication cadence. However, there is no explicit when-to-use/when-not guidance and no alternative named (e.g., 'for historical slots use gse_grid_at'), leaving the routing decision to inference.

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.