Skip to main content
Glama

Battery loss factors (MLF) by financial year

get_battery_mlf
Read-onlyIdempotent

Transmission loss factors (MLF) for one battery by financial year from FY2024-25: mlf_discharge (credits each MWh discharged), mlf_charge (bills each MWh charged), mlf_spread, and gross energy revenue at MLF 1.0 versus at the unit's loss factors (energy_rev_gross, energy_rev_mlf, mlf_effect, split into discharge_effect and charge_effect). The comparison holds dispatch fixed, so it is illustrative: a different loss factor would have changed how the unit bid. A charge factor below 1 lowers charging cost, so mlf_effect can be positive. source says whether the factor came from AEMO's published MLF list or DUDETAILSUMMARY.

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>"
    },
    "name": "get_battery_mlf"
  }
}

Input Schema

NameRequiredDescriptionDefault
duidYesBattery DUID, e.g. LIMBESS1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

With annotations already covering read-only/idempotent/closed-world, the description adds substantial non-obvious context: the FY2024-25 data start, the sign convention (a charge factor below 1 lowers charging cost so mlf_effect can be positive), the provenance switch between AEMO's published MLF list and DUDETAILSUMMARY, and the caveat that the revenue comparison holds dispatch fixed and is illustrative. Those are exactly the traits an agent could not get from the structured fields.

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?

The core purpose is front-loaded in the first clause, and the long enumeration of output fields earns its space because no output schema exists. The two closing caveats are dense but necessary; the only cost is that a single runs-on sentence mixes purpose and return-value documentation.

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?

Because there is no output schema, describing the returned fields and their signs is essential and is done well, along with the data provenance field. Minor gaps remain: it doesn't say the granularity (one row per financial year), the number of years covered, or the empty/no-MLF result, but nothing needed to invoke the tool is missing.

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?

Only one parameter, duid, and schema coverage is 100% with an inline example (LIMBESS1), so the schema carries the load completely. The description adds nothing about the parameter itself, so the baseline of 3 applies.

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 and scope: transmission loss factors (MLF) for one battery by financial year from FY2024-25, plus the derived revenue comparison fields. The output vocabulary (mlf_discharge, mlf_charge, mlf_effect) makes the tool's content unmistakable, though it never names a sibling to differentiate itself from get_battery_revenue or get_battery_optimal.

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 only implied: an agent infers it should call this when it wants loss factors or MLF-adjusted revenue for a single battery. There is no explicit when-not guidance, no mention of how it relates to get_battery_revenue's alternative revenue view, and no statement of what happens if a DUID has no published MLF.

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