Skip to main content
Glama
bchoi-qwe

aeso-mcp

by bchoi-qwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find Price Events

find_price_events
Read-onlyIdempotent

Detect sustained high pool price events in Alberta's electricity market over a time range using absolute or percentile thresholds, returning event boundaries, duration, peak/average price, and load context.

Instructions

Detects sustained high Pool Price events in CAD/MWh over [start, end). Threshold may be an absolute CAD/MWh value or a percentile (default 90th). Returns event boundaries, duration, peak/average price, and load context when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesDetect sustained high-price intervals in pool price history.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsYes
metadataYesProvenance and semantic metadata attached to dataset responses.
warningsNo
threshold_cad_per_mwhYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • 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"
+]
  2. Changed13 schema fields changedv0.2.0
    • 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
+}
  3. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent behavior, so the description's job is to add context. It does so by disclosing the threshold mechanism (absolute or percentile, default 90th) and the nature of the result (event boundaries and load context when available). This adds meaningful behavioral context beyond the 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?

The description is two sentences with no filler. The core detection behavior is front-loaded, followed by threshold semantics and the return value summary, so every sentence 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?

Given that an output schema exists, the description need not enumerate return fields in detail. It covers the interval, threshold modes, default behavior, and output categories, which is sufficient for an agent to select and invoke this tool correctly.

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 and the description does not need to compensate. It does restate the threshold alternatives and default percentile, which is helpful, but it does not add material meaning beyond the schema's already detailed 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 uses a specific verb ('Detects'), a clear resource ('sustained high Pool Price events'), and an explicit interval ('[start, end)'), which distinguishes it from sibling tools that return raw prices or market snapshots. It also states the output shape ('event boundaries, duration, peak/average price'), leaving no ambiguity about what the tool does.

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

Usage Guidelines2/5

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

The description implies the tool is for detecting sustained high-price events, but it does not explicitly state when to use this tool versus alternatives such as analyze_market_event, get_price_statistics, or get_pool_prices. No exclusions or alternative routing guidance is provided.

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

Deploy Server

Other Tools