aivy-mcp

Official

Overview Schema Source Related Servers Discussions Admin

plan_best_price_discharge

Plan battery discharge by selecting best-paid Amber intervals in a window above reserve SOC and optional minimum sell price; returns expected revenue and proposed slots without applying changes.

Instructions

Propose when to sell: picks the best-paid Amber intervals in the window (HH:MM) for the battery's usable energy above reserve_soc, optionally only above min_sell_c c/kWh. Returns intervals, expected revenue, the average it beats and proposed time_slots. Nothing is applied; apply with set_energy_mode(mode='forced', time_slots=...) after the user agrees. Hosts that support cards show the plan with an Apply button; a click on it is the user's yes.

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": {
      "site_id": "<site_id>"
    },
    "name": "plan_best_price_discharge"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	Yes
`min_sell_c`	No
`window_end`	No
`reserve_soc`	No
`window_start`	No
`battery_capacity_kwh`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Nov 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that nothing is applied, what the response contains (intervals, expected revenue, the average it beats, proposed time_slots), and how host card UIs surface an Apply button whose click counts as user consent. It stops short of permissions, failure modes, or what happens when no interval clears the threshold.

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 core action and the output shape, then the safety/next-step caveat. Dense but every clause carries information; the Apply-button sentence is slightly niche but justifies itself by defining consent semantics.

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 six-parameter optimization planner this is nearly complete, especially since an output schema exists and return values needn't be re-explained. Gaps are minor: default window behavior when window_start/end are null, units/timezone, and the role of battery_capacity_kwh.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate and mostly does: it explains reserve_soc (usable energy above it), min_sell_c (c/kWh threshold, optional), and gives a format hint for the window (HH:MM). battery_capacity_kwh is never mentioned and site_id is only implied, leaving two of six parameters to guesswork.

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?

States a specific verb and resource: 'Propose when to sell: picks the best-paid Amber intervals in the window (HH:MM) for the battery's usable energy above reserve_soc'. The 'best-paid intervals' framing implicitly separates it from the sibling plan_discharge_to_target, and the returns are enumerated so an agent knows exactly what comes back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states this is a non-mutating proposal ('Nothing is applied') and names the follow-up tool and its arguments: apply with set_energy_mode(mode='forced', time_slots=...) after the user agrees. The optional min_sell_c filter is framed as a condition ('optionally only above'), which tells the agent when to set it.

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