Skip to main content
Glama

Nyiso Lmp Zonal

nyiso_lmp_zonal
Read-onlyIdempotent

NYISO (New York) zonal LMP (locational marginal price, $/MWh) for the most recent published day, broken down by load zone (CAPITL, CENTRL, DUNWOD, GENESE, HUD VL, LONGIL, MHK VL, MILLWD, N.Y.C., NORTH, WEST). Returns LBMP, marginal cost of losses, marginal cost of congestion per 5-min interval. Use for NY wholesale electricity prices, zonal congestion analysis.

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (NY local). Defaults to yesterday — today's file may not be published yet.
zoneNoOptional zone filter, e.g. "N.Y.C." or "CAPITL". Default: all 11 zones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "date": "2024-01-15"
      +  },
      +  {
      +    "date": "2024-01-15",
      +    "zone": "N.Y.C."
      +  }
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds valuable details: returns data for 'most recent published day,' interval (5-min), and breakdowns by zone, which goes beyond 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 front-loaded with key purpose, lists zone examples, and explains return values. Every sentence adds value; no fluff.

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?

Despite no output schema, the description details return fields (LBMP, losses, congestion) and time resolution (5-min). The tool is simple with two optional parameters, and the description covers all necessary context for proper use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (date, zone) are fully described in the schema, and the description adds context: date defaults to yesterday (today's file may not be published), zone is optional with default all 11 zones. This enriches the schema.

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 clearly states the tool retrieves NYISO zonal LMP data for the most recent published day, broken down by load zone. It specifies the return values (LBMP, marginal cost of losses, congestion) and distinguishes from sibling NYISO tools by emphasizing zones and LMP.

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 provides clear use cases: 'Use for NY wholesale electricity prices, zonal congestion analysis.' However, it does not explicitly exclude scenarios or mention alternative tools, though siblings are listed separately.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.