Skip to main content
Glama

Gse Grid At

gse_grid_at
Read-onlyIdempotent

Georgia's national grid state at a specific past time, the same generation, tie-line and consumption blocks as gse_grid_now, with the same QUALITY flags, for one 3-minute slot. Sourced from the JSC Georgian State Electrosystem real-time export, which is retained for a rolling ~30 days; earlier timestamps are gone. Timestamps are Tbilisi local time (UTC+4) unless timezone is set to utc. If that exact slot was never published this reports the miss rather than substituting a nearby one.

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": {
      "timezone": "tbilisi",
      "timestamp": "2026-09-10 03:30"
    },
    "name": "gse_grid_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoHow to read the timestamp. Default 'tbilisi', which is how GSE names the files.
timestampYesThe moment to read, as 'YYYY-MM-DD HH:MM' or 'YYYY-MM-DDTHH:MM' or 'DD.MM.YYYY HH:MM'. Minutes are floored to the 3-minute grid GSE publishes on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is in retention limits, timezone defaulting, and the no-substitution rule on a missed slot. Those are real behavioral disclosures beyond the structured data. It does not say what the 'miss' response actually looks like, which is the remaining gap.

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?

Three sentences, front-loaded with what and where, then retention, then timestamp semantics. Every sentence carries information, though the first is long and packs the sibling comparison inside a subordinate clause.

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 does the work of describing the return payload by reference to gse_grid_now (generation, tie-line, consumption blocks plus QUALITY flags). Retention and timezone caveats cover the main failure modes; only the miss-response shape is left vague.

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 100%, so the baseline is 3; the description adds meaning by explaining that the timestamp is read as Tbilisi local (UTC+4) unless timezone is set to utc, and that slots sit on a 3-minute grid. It adds interpretive context rather than restating 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?

States a specific resource and scope — 'Georgia's national grid state at a specific past time' — and pins the return shape by reference to a named sibling ('the same generation, tie-line and consumption blocks as gse_grid_now'). The past-time framing makes selection against the 'now' sibling 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?

Gives a hard usage boundary: data is retained for a rolling ~30 days and earlier timestamps are gone, so the agent knows when the call will fail. It stops short of explicitly naming gse_grid_now as the alternative for current readings, leaving that inference to the reader, which keeps it from a 5.

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.