aeso-mcp

Overview Schema Source Related Servers Discussions Admin

Get System Marginal Prices

get_system_marginal_prices

Read-onlyIdempotent

Retrieve minute-level System Marginal Price (SMP) observations in CAD/MWh for Alberta's AESO market. Specify a start and end time to get interval-bounded data for up to 7 days.

Instructions

Returns AESO System Marginal Price (SMP) observations in CAD/MWh with minute-level interval boundaries for [start, end). Prefer get_pool_prices for hourly settlement prices. Timestamps are America/Edmonton. Maximum range: 7 days.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Request minute-level System Marginal Price (SMP) 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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to restate those. It adds meaningful behavioral context beyond annotations: timestamps are in America/Edmonton, intervals are [start, end) with minute-level boundaries, and requests are limited to a 7-day range.

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 three sentences with no filler. It front-loads the core purpose, then provides sibling differentiation, timezone, and range constraints, all of which are directly useful for invoking the tool correctly.

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 read-only data retrieval tool with a rich output schema and strong annotations, the description covers everything needed: what is returned, units, interval semantics, timezone, maximum range, and how to route to a sibling tool. No critical behavioral information 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 extra meaning by clarifying the inclusive/exclusive interval semantics, the timezone interpretation, and the maximum range constraint, which supplements the schema's parameter descriptions.

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 states a specific verb ('Returns'), a specific resource ('AESO System Marginal Price observations'), and clarifies the units (CAD/MWh) and interval semantics ([start, end)). It also differentiates from the closely related sibling get_pool_prices, so an agent can reliably distinguish this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent to prefer get_pool_prices when hourly settlement prices are needed, which provides a clear selection rule between the two most similar tools. It also states the timezone and maximum supported range, giving practical constraints for valid usage.

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

Deploy Server