aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Compare Market Periods

compare_market_periods

Read-onlyIdempotent

Compare aggregate pool prices and load between two Alberta market periods to reveal averages, min/max/median values, and deltas for informed analysis.

Instructions

Compares aggregate pool-price and load statistics between two America/Edmonton market periods. Returns averages, min/max/median prices, load stats, and deltas. Does not assert causation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Compare aggregate pool-price and load statistics across two periods.

Output Schema

TableJSON Schema

Name	Required	Description
`metadata`	Yes	Provenance and semantic metadata attached to dataset responses.
`period_a`	Yes	Aggregate statistics for one market period.
`period_b`	Yes	Aggregate statistics for one market period.
`warnings`	No
`load_avg_delta_mw`	No
`load_avg_pct_change`	No
`price_avg_pct_change`	No
`price_avg_delta_cad_per_mwh`	No

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"
+]

Changed13 schema fields changedv0.2.0Aug 24, 2026

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
+}

First observedv0.1.1Aug 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations by specifying the aggregate nature of the statistics, the inclusion of deltas, and the important caveat that the tool 'does not assert causation.'

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?

The description is two concise sentences. The first sentence front-loads the core action and scope, and the second adds a valuable interpretative caveat without unnecessary detail. Every phrase earns its place.

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?

With an output schema present, the description does not need to explain return values. It provides the essential information needed to invoke the tool correctly: the comparison target, the market area, the statistic types, and the causal limitation. No critical information for selecting or calling the tool is missing.

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 value by identifying the timezone 'America/Edmonton' and clarifying that the comparison is about pool-price and load statistics, which helps the agent understand the semantic context of the four date-time parameters even though the schema already defines their types and required status.

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 clearly states the tool's specific action: 'Compares aggregate pool-price and load statistics between two America/Edmonton market periods.' It names the exact resource and scope, and the comparison-of-two-periods framing distinguishes it from sibling tools like get_price_statistics or get_pool_prices, which do not emphasize dual-period comparison.

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?

The description implies a clear use case: comparing aggregate pool-price and load statistics across two distinct historical periods. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear that an agent would know when to select this tool over single-period or forecast-related siblings.

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

Deploy Server