Skip to main content
Glama
bchoi-qwe

aeso-mcp

by bchoi-qwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Explain Market Conditions

explain_market_conditions
Read-onlyIdempotent

Compare market conditions in a focus window with a preceding baseline window to get structured evidence, observed metrics, and associated changes for building your own explanation.

Instructions

Returns structured evidence for market conditions in a focus window versus a baseline window (default: immediately preceding equal-length window). Includes observed metrics and associated_changes. Does not claim causation; the calling model should produce any natural-language explanation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesRequest structured evidence for market conditions around a time window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metadataYesProvenance and semantic metadata attached to dataset responses.
warningsNo
focus_endYes
focus_startYes
baseline_endYes
baseline_startYes
notable_movementsYes
associated_changesYes
observed_conditionsYes

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

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful behavioral context beyond annotations by disclosing that the tool returns observed metrics and associated_changes without asserting causation, and that the calling model must generate any natural-language explanation.

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?

Three sentences, each carrying distinct information: the comparison and default baseline, the output components, and the critical limitation/caveat. There is no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with a fully described schema and an output schema, the description covers the default baseline and the non-causal nature of the output. It could add a little more context about what 'market conditions' evidence is intended to support, but the output schema likely supplies that detail.

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 schema already documents request.start, request.end, and the optional baseline window. The description's mention of the default preceding equal-length baseline restates information already present in the schema (baseline_start's default), adding no new semantic detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Returns') and resource ('structured evidence for market conditions in a focus window versus a baseline window'), clearly conveying the comparison task. It distinguishes the tool from a natural-language analyst by stating it does not claim causation, though it does not explicitly name or contrast a sibling tool.

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 gives clear context: use it when structured market-condition evidence is needed and a baseline comparison is desired, with a default baseline if none is supplied. It does not enumerate exclusions or explicitly name alternatives, but the boundary between this tool and a natural-language explainer is stated via the final sentence.

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