Skip to main content
Glama
bchoi-qwe

aeso-mcp

by bchoi-qwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Secondary Offer Price Limit

get_secondary_offer_price_limit
Read-onlyIdempotent

Retrieve the current AESO Secondary Offer Price Limit public report to check if the secondary cap is in effect and obtain the CAD/MWh limit when posted.

Instructions

Returns the current AESO Secondary Offer Price Limit public report: whether the secondary offer cap is in effect and the CAD/MWh limit when posted. A null limit means the cap is not in effect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRequest the current market-power mitigation public reports.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metadataYesProvenance and semantic metadata attached to dataset responses.
warningsNo
intervalsYes
report_timeNo
limit_in_effectNo
secondary_offer_price_limit_cad_per_mwhNo

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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond annotations: it defines the meaning of a null limit (cap not in effect) and frames this as the current public report. No contradiction exists.

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 with no wasted words: the operation and resource are front-loaded, and the null-limit clarification is concise and valuable. 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?

For a single-parameter, read-only report with an output schema and rich annotations, the description and schema together fully specify what is returned and how to interpret it. The current-only constraint is captured in the schema, and the null semantics are explained in the description.

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?

The input schema has 100% description coverage for the `request` object and `current_only` field, so the schema already documents the parameters. The description adds no parameter-level detail, but none is needed given the schema's clarity.

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 names a specific resource ('AESO Secondary Offer Price Limit public report') and a concrete verb ('Returns'), then specifies the exact content: whether the cap is in effect and the CAD/MWh limit when posted. It also clarifies the null-limit meaning, which distinguishes this tool from the broad sibling list.

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?

No explicit when-to-use guidance or alternative routing is provided; the description simply states what the tool returns. Use is implied by the tool's highly specific subject matter rather than contrasted with siblings, so it is adequate but not directive.

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