Skip to main content
Glama

Gse Publications

gse_publications
Read-onlyIdempotent

Reports and notices published by JSC Georgian State Electrosystem, Georgia's transmission system operator, including the Generation Adequacy Assessment (the medium and long-term supply-adequacy outlook), annual reports, independent auditor's reports, donor-organisation reports and the Strategic Environmental and Social Assessment. Also covers the operator's news and announcements. Available in English and Georgian.

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": {
      "per_page": 2,
      "category_id": 6
    },
    "name": "gse_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage. Default 'en'.
pageNoPage number, 1-based. Default 1.
per_pageNoItems per page. Default 10, max 50.
collectionNoWhich collection to list. Default 'publications'.
category_idNoFilter to one category. 3 = Annual Reports, 5 = Independent Auditor's Annual Report, 6 = Generation Adequacy Assessment, 7 = Donor Organizations' Reports, 8 = SESA, 1 = News, 2 = important news. Call with no category to see the full list in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful context about language availability and content coverage, but does not discuss pagination, filtering behavior, or response shape. It does not contradict the annotations.

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 three sentences and front-loads the core content scope. The enumeration of report types is informative but slightly list-heavy, though no framing sentences are wasted.

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 five-parameter, read-only listing tool with full schema coverage and rich annotations, the definition covers the main content domains and languages. It omits the 'projects' collection exposed by the schema and does not describe the paginated response, but the parameter schema carries those details and no output schema exists.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that the Generation Adequacy Assessment is the medium- and long-term supply-adequacy outlook and by noting English and Georgian availability, which helps interpret category_id and lang. It does not add detail for page or per_page, so it is not a 5.

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 states the resource precisely: reports and notices published by JSC Georgian State Electrosystem, and enumerates document types including Generation Adequacy Assessment, annual reports, auditor reports, donor reports, SESA, plus news and announcements. It is clear what content the tool returns, but it uses no explicit list/retrieve verb and does not name sibling alternatives.

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 guidance. The content scope implies this is the publications/news source, but the description never says to choose it over gse_tenders, gse_demand_forecast, or other siblings, and it offers no prerequisites or exclusions.

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.