Skip to main content
Glama
bchoi-qwe

aeso-mcp

by bchoi-qwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Metered Volumes

get_metered_volumes
Read-onlyIdempotent

Retrieve hourly AESO metered energy volumes in MWh by asset, filtering by up to 20 asset IDs or pool-participant IDs for targeted analysis. Unfiltered queries cover up to 16 days, with paginated results for large datasets.

Instructions

Returns hourly AESO metered energy in MWh by asset. Filter by up to 20 asset IDs or 20 pool-participant IDs (not both); unfiltered requests are limited to 16 days and all output is paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRequest metered volumes, optionally filtered by assets or participants.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPagination state for a stable in-memory report result.
metadataYesProvenance and semantic metadata attached to dataset responses.
warningsNo
intervalsYes

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. Addedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the mutual exclusivity of filters, the 16-day limit on unfiltered requests, and pagination behavior. These are non-obvious execution traits the agent needs to know.

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, no filler. The main result is front-loaded, and constraints are packed efficiently.

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 output schema and rich annotations present, the description covers essential invocation details: unit, granularity, filter constraints, date-window limitation, and pagination. Nothing critical is missing for an agent to select and call the tool correctly.

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?

The schema already covers the request object with property names and limits, so baseline is 3 at high coverage. The description adds semantic meaning by clarifying that asset_ids and pool_participant_ids cannot be combined and that omitting filters restricts the date window.

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') and resource ('hourly AESO metered energy in MWh by asset'), making it easy to distinguish from sibling tools like get_load or get_generation. The unit and granularity are explicit.

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?

Provides clear context: filters can be up to 20 asset IDs or pool-participant IDs but not both, unfiltered requests are limited to 16 days, and output is paginated. It does not explicitly name alternative tools or conditions for choosing them, so a full score is not warranted.

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