aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Get Load

get_load

Read-onlyIdempotent

Fetch Alberta Internal Load (AIL) in MW for a date range, with optional forecast. Covers up to 90 days using America/Edmonton timestamps.

Instructions

Returns Alberta Internal Load (AIL) observations in MW for [start, end). Optionally includes load forecast values when available. Timestamps are America/Edmonton. Maximum range: 90 days.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Request Alberta Internal Load (AIL) observations.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Pagination state for a stable in-memory report result.
`metadata`	Yes	Provenance and semantic metadata attached to dataset responses.
`warnings`	No
`intervals`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Aug 28, 2026

changedOutput schema / properties / metadata / properties / provider / enum

Previous value: -[
-  "gridstatus",
-  "aeso_apim",
-  "aeso_public_report",
-  "derived"
-]New value: +[
+  "gridstatus",
+  "aeso_apim",
+  "aeso_public_report",
+  "aeso_csd_archive",
+  "derived"
+]

Changed17 schema fields changedv0.2.0Aug 24, 2026

addedInput schema / properties / request / properties / limit

Added value: +{
+  "default": 500,
+  "maximum": 2000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / request / properties / offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / metadata / properties / available_series

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / metadata / properties / cache_age

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Age of the cached provider result in seconds when served."
+}

addedOutput schema / properties / metadata / properties / cache_hit
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

addedOutput schema / properties / metadata / properties / completeness

Added value: +{
+  "default": "unknown",
+  "description": "Completeness of the requested observations or series.",
+  "enum": [
+    "complete",
+    "partial",
+    "degraded",
+    "empty",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / metadata / properties / expected_observation_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / expected_observations

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / finality

Added value: +{
+  "default": "unknown",
+  "description": "Whether published observations are final or still preliminary.",
+  "enum": [
+    "final",
+    "preliminary",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / metadata / properties / missing_observation_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / missing_observations

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / metadata / properties / missing_series

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / metadata / properties / observation_type

Added value: +{
+  "default": "actual",
+  "description": "What kind of observation a response contains.\n\n``DataStatus`` predates this distinction and remains available for\ncompatibility.  ``observation_type`` should be used when a client needs\nto distinguish an actual observation from a forecast or a derived value.",
+  "enum": [
+    "actual",
+    "forecast",
+    "derived",
+    "unknown"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / metadata / properties / provider / enum

Previous value: -[
-  "gridstatus",
-  "aeso_apim",
-  "derived"
-]New value: +[
+  "gridstatus",
+  "aeso_apim",
+  "aeso_public_report",
+  "derived"
+]

addedOutput schema / properties / metadata / properties / served_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "description": "Pagination state for a stable in-memory report result.",
+  "properties": {
+    "limit": {
+      "type": "integer"
+    },
+    "next_offset": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "returned": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "offset",
+    "limit",
+    "returned",
+    "total"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "intervals",
-  "metadata"
-]New value: +[
+  "intervals",
+  "page",
+  "metadata"
+]

First observedv0.1.1Aug 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond that: exact interval semantics, timezone handling, a 90-day maximum range, and the caveat that forecast values are included only 'when available'. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, and every sentence adds necessary information: units, interval, timezone, maximum range, and optional forecast inclusion. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward read-only data retrieval tool, the description plus rich schema and annotations cover what an agent needs to call it correctly: interval semantics, timezone, range limit, and optional behavior. Output schema exists, so return structure does not need to be described.

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 descriptions already document start/end inclusivity and timezone interpretation, and include_forecast is explained. The description mostly restates these semantics rather than adding new meaning. Limit and offset are not described in the description, but their defaults and bounds are clear from schema metadata, so the schema carries the burden.

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 and resource: 'Returns Alberta Internal Load (AIL) observations in MW'. Clearly defines the data type, unit, and interval [start, end), making the tool distinguishable from related market and generation tools even without naming a sibling.

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 implies the tool is for retrieving AIL observations, with interval and forecast inclusion guidance, but it does not explicitly state when to prefer this over sibling tools like get_forecast or get_load_outage_forecast. No exclusions or alternatives are given, so usage context is clear but selection guidance is absent.

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

Deploy Server