Open Economics

Query official electricity consumption

get_epe_electricity_consumption

Read-onlyIdempotent

Retrieve monthly EPE electricity consumption and consumer counts from 2004 onward. Select a bounded period, country/region/UF geography, consumption classes, and regulated/free market. The response identifies the exact synchronized official workbook version and discloses aggregation across source system rows.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Inclusive last month, YYYY-MM.
`from`	No	Inclusive first month, YYYY-MM.
`limit`	No	Maximum rows to return.
`states`	No	Optional official state codes when geography is state.
`classes`	No	Consumption classes to include.
`markets`	No	Electricity-market segments to include.
`regions`	No	Optional official regions when geography is region.
`geography`	No	Geographic aggregation level.	country
`dataset_id`	Yes	The official EPE electricity-consumption dataset identifier.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Source-preserving data or schema payload for the selected official dataset.
`meta`	Yes	Response metadata and source provenance.
`links`	No	Related API links.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 11, 2026

addedInput schema / properties / classes / description
```
Added value: +"Consumption classes to include."
```

addedInput schema / properties / dataset_id / description

Added value: +"The official EPE electricity-consumption dataset identifier."

addedInput schema / properties / from / description
```
Added value: +"Inclusive first month, YYYY-MM."
```
addedInput schema / properties / geography / description
```
Added value: +"Geographic aggregation level."
```
addedInput schema / properties / limit / description
```
Added value: +"Maximum rows to return."
```

addedInput schema / properties / markets / description

Added value: +"Electricity-market segments to include."

addedInput schema / properties / regions / description

Added value: +"Optional official regions when geography is region."

addedInput schema / properties / states / description

Added value: +"Optional official state codes when geography is state."

addedInput schema / properties / to / description

Added value: +"Inclusive last month, YYYY-MM."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "REST-aligned Open Economics response with data, metadata, links, and source provenance.",
+  "properties": {
+    "data": {
+      "description": "Source-preserving data or schema payload for the selected official dataset."
+    },
+    "links": {
+      "additionalProperties": {},
+      "description": "Related API links.",
+      "properties": {
+        "observations": {
+          "description": "Canonical observations endpoint for this dataset.",
+          "type": "string"
+        },
+        "self": {
+          "description": "Canonical URL for this response.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Response metadata and source provenance.",
+      "properties": {
+        "dataset": {
+          "description": "Open Economics dataset identity when supplied."
+        },
+        "provenance": {
+          "description": "Upstream source URLs, versions, timestamps, and methodology details."
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered. The description adds genuine behavioral context beyond that: the response identifies the exact synchronized official workbook version and discloses aggregation across source system rows, which is provenance information an agent would not otherwise have.

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, no filler, front-loaded with the resource and time span before the filtering guidance. Slightly dense jargon ("synchronized official workbook version") but each sentence carries information.

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 an output schema present, return-value explanation is not needed, and the description covers scope, filters, and data provenance. Only the absence of routing guidance relative to sibling tools keeps it short of complete.

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 baseline is 3. The prose adds only marginal meaning over the schema — the 2004 lower bound and the UF/region/state geography framing — while mostly restating the filter parameters already fully documented in 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 verb (retrieve) plus resource (monthly EPE electricity consumption and consumer counts) and scope (from 2004 onward). The EPE dataset naming cleanly separates it from the many other Brazilian official-data siblings (BCB, IBGE, CVM, Tesouro, etc.).

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?

The description tells the agent what to select (bounded period, geography, classes, market) but never says when to prefer this tool over search_official_data or describe_official_dataset, nor any exclusions or prerequisites. Usage is implied by the dataset name rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Open Economics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.