Skip to main content
Glama

Gnerc Station Generation

gnerc_station_generation
Read-onlyIdempotent

Monthly electricity generation for individual Georgian power stations, Enguri HPP, the Vardnili cascade, Khrami 1 and 2, Zhinvali, Gardabani thermal 1 and 2, the Kartli wind farm, named solar plants, plus national supply, consumption, import, export and named large direct consumers, in million kWh. Sourced from the Georgian National Energy and Water Supply Regulatory Commission (GNERC) actual-balance workbook, covering 2015 to 2026. Station names are published in Georgian script; each row keeps its original name and its position in the balance hierarchy.

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": {
      "year": 2026,
      "query": "ენგურ"
    },
    "name": "gnerc_station_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year, 2015-2026.
limitNoMaximum rows to return. Default 100, max 400.
queryNoOptional substring filter on the Georgian row label, e.g. "ჰესი" for hydro stations or "ენგურ" for Enguri. Matching is case-insensitive and accent-blind on the Georgian text as published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly=true, idempotent=true, destructive=false, and openWorld=true. The description adds meaningful context beyond those annotations: data source (GNERC actual-balance workbook), year coverage (2015–2026), units (million kWh), Georgian-script station names, and preservation of original row names and hierarchy position. It does not discuss pagination or response limits, but the safety profile is already covered.

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 front-loaded with the core resource and coverage, and the station list earns its place by showing what is included. It is somewhat run-on and dense, but there is little wasted wording for a dataset with this many named entities.

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 read-only data-retrieval tool with no output schema, the description supplies the source, units, year range, geographic/script detail, and row-structure context. It could do more to explain the output columns and how national aggregate rows differ from station rows, but it is substantially complete for an agent to select and invoke the 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?

Schema description coverage is 100%, so the schema already documents year, limit, and query. The description reinforces that station names are published in Georgian script, but it does not explain the query parameter's filtering behavior or the limit parameter. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 identifies the resource and scope: monthly electricity generation for named Georgian power stations plus national supply, consumption, import, export, and direct consumers, in million kWh. It does not explicitly distinguish itself from the sibling gnerc_prices tool, but the content domain (generation balance vs. prices) is evident.

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 by the detailed dataset description: an agent can infer this tool is for station-level generation and national balance data. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no mention of the sibling gnerc_prices alternative for price data.

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.