Skip to main content
Glama

get_bpdb_power_generation

Read-onlyIdempotent

Retrieve daily electricity generation (installed/derated capacity MW, day-peak MW, and evening-peak MW) across 40 Bangladesh Power Development Board (BPDB) power plants. Use for national grid load, power plant output, or energy sector queries. Read-only, updated every 2 hours. Returns aggregate peak MW totals and plant-level generation records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
plantNoOptional power plant name substring filter (e.g. 'Payra', 'Rampal', 'Ashuganj', 'Kaptai'). Omit to return all 40 power plants and aggregate MW totals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / plant / description
      Previous value: -"Power plant name filter"New value: +"Optional power plant name substring filter (e.g. 'Payra', 'Rampal', 'Ashuganj', 'Kaptai'). Omit to return all 40 power plants and aggregate MW totals."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to carry the full safety burden. It adds useful context beyond annotations by disclosing the update cadence ("updated every 2 hours") and the return shape (aggregate peak MW totals plus plant-level records). It still omits details such as rate limits or pagination, which keeps it from being exhaustive.

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 retrieval action and metrics, followed by usage and operational details in three efficient sentences. It is mostly concise, though "Read-only" partly repeats what the annotations already declare.

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 tool with one optional parameter and no output schema, the description covers coverage, key metrics, freshness, and return structure well. It leaves minor ambiguity about whether "daily" means only the current day or historical daily records, but the essential information for invocation is present.

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 optional plant parameter is already fully documented in the input schema. The description mentions the 40-plant scope and distinguishes aggregate totals from plant-level records, but it does not add filtering syntax or behavior beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: "Retrieve daily electricity generation" across 40 named BPDB plants. It also names the exact metrics returned, making it clearly distinguishable from sibling tools such as weather, air quality, or river-level services.

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?

It gives clear usage contexts: "national grid load, power plant output, or energy sector queries." It does not explicitly state when not to use the tool or name alternatives, but the sibling domains are sufficiently distinct that this omission is minor.

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.

Resources