Skip to main content
Glama

Battery network access (binding constraints)

get_battery_network_access
Read-onlyIdempotent

Network access for one battery by DUID over a date window: the same exposure shares as get_network_access, a 12-block (2-hour, market time) time-of-day profile for discharge and charge limits, the five constraints that bound most often with AEMO's descriptions (these name the lines and outages involved), commissioning_days, and the current financial year's loss factors with their effect on energy revenue versus an MLF of 1.0. Exposure, not lost revenue. A high all-interval share with a low top-price share means the limits fall in low-price hours (often midday). Minimum window 30 days (shorter is widened); data from July 2024.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "duid": "<duid>",
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "get_battery_network_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
duidYesBattery DUID, e.g. KESSB1. Use list_bess_units to find it from a station name.
date_toYesEnd date YYYY-MM-DD.
date_fromYesStart date YYYY-MM-DD. Ranges under 30 days are widened to the last 30 days ending date_to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low; the description adds real behavior beyond that: a 30-day minimum window that silently widens shorter ranges, data coverage starting July 2024, and explicit interpretive guidance ('Exposure, not lost revenue', and how to read a high all-interval share with a low top-price share). It still says nothing about response size, latency, or what happens for an unknown DUID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and scope, and the terse 'Exposure, not lost revenue' plus the share-interpretation sentence earn their place. The opening sentence is a long comma-chained list of outputs that is dense but not redundant; minor cost in readability rather than wasted words.

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?

There is no output schema, so the description carries the full burden of describing return content, and it does: exposure shares, the 12-block discharge/charge limit profile, five named constraints with line/outage descriptions, commissioning_days, and loss factors versus an MLF of 1.0. Combined with the coverage window and window-minimum rules, an agent has enough to call it and interpret the result.

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 coverage is 100%, so the schema already documents duid, date_from, and date_to, including the widening rule. The description restates the 30-day window and July 2024 floor but adds no new parameter-level meaning (no DUID format nuance, no timezone or market-time note beyond the 2-hour block naming). Baseline 3 applies where the schema does the heavy lifting.

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?

States a specific resource ('Network access for one battery by DUID over a date window') and then enumerates the concrete outputs: exposure shares, a 12-block time-of-day profile, five binding constraints with AEMO descriptions, commissioning_days, and loss factors. It also signals overlap with the sibling get_network_access ('the same exposure shares as ...'), which helps distinguish it, though it never frames that as a routing choice.

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?

Usage is implied rather than stated: the mention of 'the same exposure shares as get_network_access' hints this is the single-battery variant, but there is no explicit 'use this instead of get_network_access when...'. The operational caveats (minimum 30-day window, data from July 2024) are useful preconditions but are data constraints, not when-to-use guidance.

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.

Resources